[Octave-bug-tracker] [bug #36658] acceptance of "global a = b"

[Rik]

Follow-up Comment #3, bug #36658 (project octave):

What behavior is desirable?  It seems slightly more logical to me that if the
variable is already global, then the scoping operator is ignored and the
assignment takes place.

Sample Code:


octave:1> b = 2;
octave:2> global a = b
octave:3> a
a =  2
octave:4> b++;
octave:5> global a = b
octave:6> a
a =  2


I would vote for having a = 3 on the last line.

A second question is why the global scoping operator suppresses normal output.
 Usually a line which isn't terminated with a semicolon echoes its output, but
that isn't the case for global.

More Sample Code:


octave:1> x = 1
x =  1
octave:2> global y = 2





    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/