Re: Unclearable global variables?

[pkienzle]

I agree that 'save file' should save all variables, including
globals.  

IIRC, at the time I wrote edit 'save file v' would save all 
globals in addition to v, and this is the behaviour I was 
questioning.  It does not anymore, and  the current 
behaviour is what I expect.

- Paul


> address@hidden wrote:
> 
> >This method has a couple of advantages:
> >
> >1) the value doesn't get stored during save like
> >global values do (did?)
> >
> >2)  the values are available without having to
> >say 'global value'
> >
> >The second could also be considered a disadvantage,
> >but in that case namespace support could be added
> >to octave to address it.
> >
> >-Paul
> >
> >  
> >
> 
> Paul,
> 
> If mlock marked the symbol table entry as "eternal" the variable would 
> be considered as a builtin a wouldn't be saved, and you wouldn't have to 
> say "global var" either. Not saving the variable is not necessarily an 
> advantage though in my opinion, I'd prefer is such user eternal 
> variables were a new variable attribute that had the properties of 
> builtins but were saved... So the load/save code would need to be 
> modified slightly, so that it could mark such an attribute...
> 
> Regards
> David
> 
> 
> 
> 
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
> 
> Octave's home on the web:  http://www.octave.org
> How to fund new projects:  http://www.octave.org/funding.html
> Subscription information:  http://www.octave.org/archive.html
> -------------------------------------------------------------
> 



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------