long variable error... a fix needed for 5.5.

[Fairlight]

>From inside the gravity well of a singularity, John Esak shouted:
> 
> I think having the variable work as one would expect 2 character variables
> to work should be the goal... regardless of complications... The other mode
> of only allowing them to carry one value might have some utility... if so,
> let's hear it.

I understood 95% of what you wrote.  Some parts are hazy because I never
used break-point reporting stuff.  I understand the basic problem though,
given the examples.

My opinion would be that declared variables should behave identically to
undeclared dummy variables in all externally observable respects.

The question of GLOBAL in the DECLARE on an automatic table is really a
matter of placing one additional stricture on the developer in making sure
that they declare those particular variables in question as EXTERN in their
input and other tables.  But at least you'd get the expected behaviour, and
then the declaration location is simply the developer's lookout, so long as
it's documented accordingly.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html