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

[Levente Torok]

Hi Guys,

I was offline for about a week time. Sorry for not being helpful
during that time.
However, as I see John have found the heart of the bug. Thanks.

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

If you don't see this that much important, then I suggest this pattern:

octave:1> global a=2
octave:2> global a=3
octave:3>  a
3
since the worst in "a = 2" case would be that, the second global
statement would be totally misleading since it is accepted however the
equation doesn't take effect.

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.

Cheers,

Lev

On Thu, Jun 28, 2012 at 12:02 PM, Jacob Dawid <address@hidden> wrote:
> Update of bug #36658 (project octave):
>
>              Assigned to:                    None => jacobdawid
>
>     _______________________________________________________
>
> Follow-up Comment #1:
>
> Hello Lev,
>
> I could not reproduce that behaviour. Could you write a few lines of script
> that will reproduce that behaviour you mentioned?
>
>     _______________________________________________________
>
> Reply to this item at:
>
>   <http://savannah.gnu.org/bugs/?36658>
>
> _______________________________________________
>   Nachricht gesendet von/durch Savannah
>   http://savannah.gnu.org/
>