[Octave-bug-tracker] [bug #56809] Dots in script file names should be allowed

[John W. Eaton]

Follow-up Comment #6, bug #56809 (project octave):

I agree with Mike.  I don't think we want to go down this path.

Script file resolution only happens at execution time, not when the code is
parsed.

AFAIK, the only time we care about whether a symbol is defined as a variable
is to determine whether to parse something like


ls -1


as a command, equivalent to the expression "ls ('-1')", or as a subtraction. 
And that only happens at the command line, not inside scripts or functions. 
And it happens when the expression is parsed, not when it is executed.

Even if you limit your proposal to the command line, you will have some
trouble if you expect it to work for spaces.  Currently, the expression


foo bar


is equivalent to "foo ('bar')" if foo is not defined as a variable (again,
*only* at the command line).  Now we would attempt to execute the script "foo
bar.m" if the evaluation failed to find a function "foo"?

You are free to experiment with this idea and it may be possible to implement
in some limited way but I don't think it is a good feature to add to Octave.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56809>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/