PureBasic Forums - English

Why does
Goto end;
End:
Appear in the syntax conversion?

How does the debugger work with the C emit option vs FASM?

goto end: is always generated when using ProcedureReturn, even if there is no code in between (last statement of the procedure). It is suppressed by the C optimizer, don't worry. The debugger works the same, but some functions/check are not yet supported.

If you have a bigger project with lots of includes, is the Purebasic compiler going to crunch that into a single C code file? Or will the include structure persists? Because only that way you will have fast compiling times when you change just one file.

Yes, makes sense for the C optimizer.
I also like the C format you showed. Allman style is by far the easiest to read.

NicTheQuick - SQLite also does an amalgamated C file prior to compilation and it is indeed slow to compile.

skywalk wrote: Fri Apr 23, 2021 1:16 pmI also like the C format you showed. Allman style is by far the easiest to read.

Nice. I didn't know about the names of these styles. I prefer K&R. It's more compact and also easy to read.

Trust me, K&R is horrible when the code gets large and inline comments and multiple developers.
Allman solves all that noise.

NicTheQuick wrote: Fri Apr 23, 2021 1:29 pmI prefer K&R. It's more compact and also easy to read.

+1

@skywalk: 2:1

Fred's code was Allman sooooo, 2=2, tie!
But look to the polling and see Allman wins there too.

skywalk wrote: Fri Apr 23, 2021 1:38 pmFred's code was Allman sooooo, 2=2, tie!
But look to the polling and see Allman wins there too.

Well, maybe the poll is that weird with its 7 digit percentage numbers because he uses Allman

I didn't know these styles had names (thanks skywalk)
I also still prefer Allman to K&R although the latter is more readable when folded.
However, when I look at the examples from a distance, GNU indent style seems to be the best (PB display vertical lines, so more easy to read).

@Fred: Do you have tested with PellesC compiler (for Windows version). It's very fast but is he compatible with libs ? and is license and author agree ?

Hi!
I've just read about the plans to implement a c backend.
I enjoy!

NicTheQuick wrote: Fri Apr 23, 2021 1:03 pm If you have a bigger project with lots of includes, is the Purebasic compiler going to crunch that into a single C code file? Or will the include structure persists? Because only that way you will have fast compiling times when you change just one file.

Unfortuntately, PureBasic is not built at all to generate several objs, so it is not possible.

Do you suggest we collapse our lib's to a dll or can we create static libs in the future?

Will we be able to procedurereturn structs?
In C it's possible, so that could be a thing, or?

skywalk wrote: Sun Apr 25, 2021 4:19 pmDo you suggest we collapse our lib's to a dll or can we create static libs in the future?

Static libraries can be created even now.
This is done by the tools TailBite, coffit and etc. But unfortunately they are very dependent on the PB static libraries.
Switching to C won't change anything and the dependencies will remain.