[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: Mike Miller
Subject: [Octave-bug-tracker] [bug #55667] Conflict between package namespace and function name
Date: Thu, 7 Feb 2019 13:16:39 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.81 Safari/537.36

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

I would appreciate some help in understanding the tradeoffs and options here.
I do understand the conflict being discussed here and why it's a problem with
overloaded names. What I would like help with is understanding how I should
proceed with the Python interface.

I need a way for any call that begins with "py." to be dynamically interpreted
as a lookup on a Python function or class name. If there were a way to somehow
register a proper classdef +py namespace with a dynamic name resolution hook,
I could do that.

At the moment, I have an Octave class named "@py". So calling "py.int"
instantiates an Octave @py object and then does a subsref on it, at which
point I can pass that on to my Python name resolution function.

If we take away inline dot indexing of function calls, I am not sure how else
I can implement this in Octave right now. Any suggestions? We can certainly
take this offline and discuss in more detail if needed.


Reply to this item at:


  Message sent via Savannah

reply via email to

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