[Top][All Lists]

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

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

From: Olaf Till
Subject: [Octave-bug-tracker] [bug #55667] Conflict between package namespace and function name
Date: Tue, 12 Feb 2019 16:02:35 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #8, bug #55667 (project octave):

If foo().index and foo(some,arguments).index could be kept working, even if
foo.index can't (for a function foo), I think that would help much.
Regarding your example with dir(), I don't see the reason for assuming nargout
== 0 in a call like foo().index ...

Well, I counted less than 100 lines in package optim containing 



value(index)(index) .

But using subsref() or some streamlined version of it as an alternative would
not improve readability...


Reply to this item at:


  Message sent via Savannah

reply via email to

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