[Octave-bug-tracker] [bug #54052] the global statement clears previously assigned values

[Michael Godfrey]

Follow-up Comment #18, bug #54052 (project octave):

Rik and John,

I just found that there has been a change in the handling of global since 16
Jun. The change in this report could be the cause.

With a system build on 16 June I could reference a global
in a script which did not itself contain a global declaration.
Now that does not work. It is necessary to declare the global
in the script even though the variable is shown as existing
(as global) in a whos before invoking the script.

This change may be intentional and I would agree if it was
intended. Just thought it would be good to point out the
change.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54052>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/