>   I think that it would be fair to _assume_ that block starts and ends are
> always located in the same file. This probably will not break any logical
> SDL script and is a very rational standard limitation to make.
>   The big advantage of this is, of course, speed. If we are skipping a
block
> of code, we don't need to read any possible #includes in this block
because
> the specs say that there can't be anything interesting in the include
anyways.
>
>   I don't see any advantage of supporting the feature that, for example,
> an #if starts in one file and the correspondent #end is in another file
> (of course you could invent lots of artificial examples, but I don't think
> there is any real useful example).

I have written such a script and it's very useful! It's not #if and #end,
but { and }. I think it's not a big difference.


#include "part1.inc"   //Camera, lights etc. and...
//an union is started!

---Write your object---

#include "part2.inc"   //The union is modified and ended

Post a reply to this message