octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #40368] octave_config_info() should be read-on


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #40368] octave_config_info() should be read-only
Date: Fri, 25 Oct 2013 15:19:05 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130810 Firefox/17.0 Iceweasel/17.0.8

Follow-up Comment #4, bug #40368 (project octave):

A warning about creating a variable with the same name as an existing function
is probably not workable.  For efficiency, we'd probably want to do the check
in the parser, not the evaluator, but the list of visible functions might not
be the same when a statement is parsed vs. executed.

We do currently have a warning for the implicit conversion of the character
array index to a numerical value, but it is disabled by default for improved
Matlab compatibility.  I don't remember whether that default was chosen
because of a complaint about compatibility, or if it was just something we did
so that Octave's behavior would match Matlab.

I suppose it would be possible to warn about indexing with a character
variable in addition to the warning about converting the index to a number.  I
don't know whether that would generate complaints about unwanted warnings from
Matlab users.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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