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

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

[Octave-bug-tracker] [bug #55667] Conflict between package namespace and


From: Guillaume
Subject: [Octave-bug-tracker] [bug #55667] Conflict between package namespace and function name
Date: Thu, 7 Feb 2019 08:37:48 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

URL:
  <https://savannah.gnu.org/bugs/?55667>

                 Summary: Conflict between package namespace and function name
                 Project: GNU Octave
            Submitted by: gyom
            Submitted on: Thu 07 Feb 2019 01:37:46 PM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: Guillaume
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

There is a conflict between package namespaces and functions with the same
name, due to the "chaining" feature Octave implements to reference the output
of a function.

Use the following toy example:


>> mkdir +octave
>> system ("echo function octave, disp('package'); > +octave/octave.m");
>> system ("echo function octave, disp('function'); > octave.m");


In Octave:


>> octave
function
>> octave.octave
function
error: can't perform indexing operations for <unknown type> type


and Matlab:


>> octave
function
>> octave.octave
package
>> import octave.*
>> octave
package







    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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