[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Torok Levente
Subject: [Octave-bug-tracker] [bug #36658] acceptance of "global a = b"
Date: Mon, 02 Jul 2012 06:35:55 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.47 Safari/536.11

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

Sorry, I was offline for about a week time.
As I see John have pointed out the heart of the bug. Thanks.

I don't know how matlab handles global statement but I should give priority to
their solution.

If you don't see this that much important, then I'd suggest the a = 3 pattern,
too, since "a = 2" case would be very misleading.

The other reason I would suggest  "a = 3" is that.
I usually collect all the interactively written commands in a text editor and
run it as a script, later.
Usually, I run it many times with slight modifications and  if it has a global
statement at the beginning it would cause me a trouble since the second run
would have effect on the value of the variable.

I would vote on 13.
What would make you think of 42, other than universe and everything?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]