Because the macros are only one piece of the puzzle on the road to have a single file (see first post).
Because compilerif have so many possible conditions it can be tested against, and I should implement them all.
CompilerIf SizeOf(structurename) = 24
IncludeFile #PB_Compiler_FilePath + "..\code\foo.pb"
IncludeFile #PB_Compiler_FilePath + "bar.pb"
Because PureBasic is not immutable, so I would have to keep up with any new addition / variation to the above features.
But above all because Fred has access to all this already, he need to output the result, and any change would be automatically included for the next version.
For me it's not trivial and I would hate to spend the time to do this just to find it implemented in the next version (hence the naive question I asked again here... didn't have many hopes but not asking it it's a sure way to not have it answered).
In short, for me it's not "so worth" the effort, since I can do something else more useful for me in the meantime. Would I like it ? Yes. I want to do it myself ? No. Will I change my mind ? Depends on what I'm doing at a certain time. Would I shameless use the code from someone else ? Certainly and thankfully.
There are many routines to make "one single file from all the includes" already posted in the forum, but no one works AFAIK.
I still have hope to see it someday because this is not something only I would appreciate, can be really useful to make many interesting tools.
That's my answer