PureBasic Forums - English

I'd like to have a new compiler option, which causes the compiler to preprocess the
sourcecode and output the code into a new file without actually compiling it.
With preprocessing I mean to instantiate all macros and constants as well as executing
conditional clauses like CompilerIf. It should also merge all included files into a single one.

EDIT: It should probably also strip all comments from the source code...

Why? Because that would make it easier to process the code further with own tools

I would like that too, for the same reasons.

When macros are still not expanded, the source can be really a mess to parse..

+1 - Very good idea!
As an addition we could select what should/shouldn't be preprocessed: Constants, Macros, CompilerIfs, Includes...

How would you propose this to work for include files? Or data sections?

From what i understand, it would output a very big .pb file with all macro/constants/compilerdirectives/includes resolved, right ? Could be interesting.

Yes, that's what I mean. Almost every C and C++ compiler has this feature - some even
have a seperate executable just for preprocessing the code (e.g GCC cpp.exe).

I like the idea.
Calling XIncludeFile at the start of a new project makes the coding fast and easy, but moving by hand the needed parts from big includes (in my case, 20000 lines with lots of procedures, constants, macros, structures, prototypes and globals) to the main source is a pain.
____________
There's always someone with a bigger IncludeFile.

I'd like to see this, too. Perhaps for the next beta?

+1

that would be great!

+1

TIA & Greetings ... Kiffi

I could really use this! Needless to say, writing a PB syntax converter is not trivial.
Debugging complex macros would be so much easier and stepping through flattened code would be more fluid for complex problems and many includes. I have to sometimes close the IDE when debugging fails after multiple runs of stepping and exiting and jumping to includes.

I see less benefit to stripping the comments though. We can do that already with small code.

skywalk wrote: I see less benefit to stripping the comments though. We can do that already with small code.

I absolutely agree comments should not be stripped. They could be there for more reasons then just remarks: markers, documentation generation, pseudo-language processed by a parser, etc. and nobody beside me can decide if they can be useful in the final single-source-all-included or not.

It's trivial to remove them if you want to do so.

This would be really nice for debugging macros, i like that idea. If a macro drives me crazy I have to replace it at the moment by hand to debug it

Bump.

Just found out today that this feature would save me a lot of work.
Why? I just loaded an old source of mine that used an IncludeFile.
That IncludeFile has now changed dramatically from what it was
originally, meaning the old source won't compile with it anymore.

If a pre-processor option existed, then my old source would have
had code from the old IncludeFile in it, which means I could still
compile the old code today without problem. Instead, I now have
to fix the "broken" new IncludeFile to work with it.

So yes, please implement a pre-processor output very soon.
It means that what we compile, can be forever stored as a "gold"
single source file of that app. This is extremely important.

+10

For a time even KCC understand what the MASTERS say
Because i have asking exactely the same thing there are 5 years in 2009 in the french forum
http://www.purebasic.fr/french/viewtopi ... 14#p105514

And even FRED answer me, perhaps a futur version

FRED wrote:Faudrait une sortie préprocessée du code source, mais pour l'instant PB ne permet pas ca.. Peut etre pour une prochaine version !

http://www.purebasic.fr/french/viewtopi ... 31#p105531

I'm happy, because i see KCC ask not alway, only shit question
FRED never listen little KCC.. perhaps this time....