|
From: | Michael Godfrey |
Subject: | [Octave-bug-tracker] [bug #54052] the global statement clears previously assigned values |
Date: | Sun, 5 Aug 2018 12:49:42 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36 |
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/
[Prev in Thread] | Current Thread | [Next in Thread] |