[Top][All Lists]

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

[Octave-bug-tracker] [bug #56881] Command line functions are visible fro

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #56881] Command line functions are visible from m files
Date: Thu, 12 Sep 2019 15:35:47 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.75 Safari/537.36

Update of bug #56881 (project octave):

                Severity:              3 - Normal => 1 - Wish               
                Priority:              5 - Normal => 3 - Low                
                  Status:                    None => Need Info              


Follow-up Comment #2:

This seems like a feature of the language to me and not a bug. Any function,
whether on the load path or on the command line, is defined in the same shared
global namespace.

If a user creates a 'max.m' function or script file, it shadows the built in
function 'max'. The same is true for defining a command line function 'max'. I
don't see a difference between these two scenarios. The best advice is always
to avoid shadowing standard function names.

Can you explain a use case that makes this a more severe problem for command
line defined functions?


Reply to this item at:


  Message sent via Savannah

reply via email to

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