"Kenneth" <kdw### [at] gmailcom> wrote:
> I was thinking the same thing: something built-in. HOW to do it-- and how
> difficult it would be to code without introducing other problems-- are the
> bigger questions, of course ;-)
Seems to me (a non-source-code-programmer) that it would work as part of the
#include directive itself, and we already have internal things like recursion
stacks, etc. So it wouldn't really be a problem to prevent multiple parsing of
As for parse time, how much extra could there possibly be to check the include
stack to see if the file has been included yet, or if the "view include stack"
flag is set or not?
But perhaps for some reason it's non-trivial.
Post a reply to this message