Stack Level Local/Globals

[Dennis Brown]

Ok folks,

I posted the following BZ for the stack level variables.  Vote for it  
if you want it.

Dennis

------------------------------------------------------------------------ 
-------------
http://support.runrev.com/bugdatabase/show_bug.cgi?id=2975

            Summary: Stack scope variable declarations
            Product: Revolution
            Version: 2.6
           Platform: All
         OS/Version: All
             Status: UNCONFIRMED
           Severity: enhancement
           Priority: P2
          Component: Transcript Language
         AssignedTo: engineteam at runrev.com
         ReportedBy: see3d at writeme.com
          QAContact: enginebugs at lists.runrev.com


The stack scope variable (I am not sure what it should be called)  
just has the
scope of a single main-stack and sub-stacks.  This means that I could  
assign
"global" names to a project without having to take into consideration  
global names
that may have been used by someone else.  This seems like the missing  
scope piece
that would simply solve many problems.  It was not my idea  
originally, but I just
seems right.

Global variable = Scope across all stacks --are a pain to use because  
the scope is
too broad so they need special naming conventions.  They are all  
right for a stand
alone, but DreamCard users don't make stand alones and run in the  
IDE.  Loading
several stacks at the same time is not unusual, but the potential for  
global
conflicts is great and a pain to debug.  Tool makers also have to  
deal with this problem.

Stack scope variable =  Scope across sub-stacks --this is the missing  
scope that
could replace globals in most situations.  The stack variable would  
not conflict
with any other mainstack projects in memory.

Dennis

----------
Posted by RevZilla 2.0.3



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.