> Here's youre wrong assumption: Only macros defer execution of 
> "preprocessing"
> statements. #declares just defer the "materializing" of already built 
> scene
> objects by instead storing them in variable space.

I understand how it works.

I just think that a declare should look for closures of control structures 
after
finding an identifier. I don't think you should just queue a pointer to the 
next
identifier. It works, but it's hardly what most people expect. In 
particular,
in a large file it can be very hard to find a typo (user error) related to 
this
behavior since it raises no parsing errors. It would be reasonable to add
warnings on use of declares containing control structures, even if it's 
decided
not to change the behavior.

Post a reply to this message