octave-maintainers
[Top][All Lists]
Advanced

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

Re: More GUI talk...


From: Søren Hauberg
Subject: Re: More GUI talk...
Date: Sun, 30 Mar 2008 18:50:49 +0200

søn, 30 03 2008 kl. 10:34 -0400, skrev John W. Eaton:
> On 30-Mar-2008, Søren Hauberg wrote:
> 
> | When the user enters a command into the GUI it is then evaluated with
> | "eval_string".
> 
> The problem with this method is that it fails for partial statements.
> You won't be able to write
> 
>   if (some_condition) RET
>     do_something (); RET
>   endif
> 
> in your GUI input box.

Would it be possible to have a function:

  bool eval_line (std::string line)

that parsed 'line'. If 'line' is fully parsed such that the actual
computations begins, the function returns 'true'. If instead 'line' is
not fully parsed (such as in your example above) it is saved, and the
function returns 'false'. Wouldn't that make it possible to work with
partial statements?

> So I think the first thing to start looking at if we really want a
> fully functional integrated GUI is to make Octave thread safe.
I guess it would be great if Octave was thread safe (then we might even
have threads available in the language itself), but getting thread
safety right is usually quite hard.

Søren



reply via email to

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