octave-maintainers
[Top][All Lists]
Advanced

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

Re: Eliminating Singleton Objects


From: John W. Eaton
Subject: Re: Eliminating Singleton Objects
Date: Fri, 28 Apr 2017 11:41:33 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0

On 04/28/2017 07:04 AM, Olaf Till wrote:
On Tue, Apr 25, 2017 at 03:43:20PM -0400, John W. Eaton wrote:
One question is what should happen to DEFUN functions called using feval?
We can provide an interpreter::feval method that can pass a pointer to the
interpreter object, but the current feval function would not do that.  Is
this a problem for existing user code

Probably yes, at least potentially.  In remote execution with the
'parallel' package, each command is executed with Octaves eval_string
function.  The remotely executed command can principally call any
function in any package, so it may call a package function which is
already revised to access the loadpath via this planned pointer to the
interpreter.

Any function that uses eval or feval has always needed the interpreter to exist ("interpreter" meaning the symbol table, load-path, etc.). The difference is only whether those things are accessed globally or as members of an interpreter object. If you are currently calling eval or feval, then the fix would be to call interpreter->eval or interpreter->feval instead.

jwe




reply via email to

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