Welcome! Log In Create A New Profile

Scoping rules for TEXMAP
avatarOctober 09, 2012 09:32AM
This is a proposal for changing the scoping rules for TEXMAP:

Add bolded text:

This texture will remain in effect until:
  • An END is given within the current file
  • The file in which the START is located ends
  • A STEP command is reached
The texture will remain active when processing an included file unless overridden within that file.

and change:

The END command stops using the current texture and restores the previous texture to current status. This means that nested commands with START will form a stack of textures and the END command will pop those textures. However, END cannot appear in a different file from START. If an END command is given in a sub file without a START having been given in that same file, the END stops the use of a texture specified in a calling file, then that texture will be restored to use when the sub file is exitedhas no effect.

These scoping changes are critically important to implementing a hierarchical, object-oriented model to textures. It will be impossible for me to implement the standard as it currently exists. I already have a working implementation of the changes described above (*).


(*) with the exception of the stack behavior for nested textures, which is a simple enough addition
Scoping rules for TEXMAP Allen Smith1241October 09, 2012 09:32AM
Re: Scoping rules for TEXMAP Roland Melkert469October 09, 2012 11:39AM
Re: Scoping rules for TEXMAP Allen Smith449October 16, 2012 10:10AM
Re: Scoping rules for TEXMAP Travis Cobbs463October 18, 2012 03:50PM
Re: Scoping rules for TEXMAP Orion Pobursky392October 25, 2012 09:17AM
Re: Scoping rules for TEXMAP Allen Smith403October 25, 2012 11:43AM
Re: Scoping rules for TEXMAP Travis Cobbs887October 26, 2012 12:36PM

Sorry, you do not have permission to post/reply in this forum.