Re: Passing variables up to the GUI

[John W. Eaton]

On 04/12/2013 10:39 PM, John W. Eaton wrote:
> On 04/12/2013 10:31 PM, Daniel J Sebald wrote:
>
> > There is no requirement that such a function behave exactly as the
> > interpreter that the user has. As with the "corefeval" I proposed the
> > other day, it is that underlying builtin code that is what the GUI has
> > interest in. So, the commands that go from the GUI's internal access
> > bypass that first level of indirection that otherwise would be M-script
> > overrides, variable overrides, etc. Neither would these commands appear
> > in the history list. The best way to describe "corefeval" is that
> > builtins cannot be overriden.
>
> Maybe we can consider something like that later but I don't have time
> now to think about that kind of change or try to make it work.

But, one quick question about what you've proposed.  If you send a 
command like

  clear x

to the interpreter, how does it know to bypass variables for the symbol 
"clear" but not "x"?  Perhaps you can describe something that will work 
for a simple case like this.  Will it generalize to any arbitrarily 
complex list of statements?

Since you are calling your function "corefeval", do you see this as 
something that is only intended to call functions, or is it supposed to 
evaluate arbitrary expressions?

jwe