1. I've got a problem using the new editor
Hi, I downloaded David Cuny's GUI editor, the newest one that had
really good reviews. I tried running it at the DOS prompt using ex EE
but I got this error message:
c:euphoria/download/gui/ keys.e:359
call_proc has not been declared
call_proc(editorClockID, Null)
Thanx in advance for anyone who can tell me how to get around this!
Rafael
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
2. Re: I've got a problem using the new editor
>Hi, I downloaded David Cuny's GUI editor, the newest one that had
>really good reviews. I tried running it at the DOS prompt using ex EE
>but I got this error message:
>c:euphoria/download/gui/ keys.e:359
>call_proc has not been declared
> call_proc(editorClockID, Null)
>Thanx in advance for anyone who can tell me how to get around this!
>Rafael
call_proc () and call_func () are *new* routines available since version 2.0
alpha.
The most recent version is the release version 2.0.
You can get the latest version at:
http://members.aol.com/FilesEU
Call_func () and call_proc call a routine based on its *index*. Yes, we now
have routine pointers.
You ask for a pointer like this:
my_integer = routine_id ("my_procedure")
Then you can call that procedure on the normal way or on the *new* way:
call_proc (my_integer, my_arguments)
Why is this introduced?
So we can program OO.
So we can have mutal recustion. (routine a calls routine b which calls a
again, etc.)
Off course it also has many other advantages, because of the dynamicy it
offers.
We now, for example, have a sort routine that can work with *any* custom
compare () routine. Normally, after you would have overwritten the built-in
compare () function, you can not overwrite it again. Now you simply pass the
integer. See the potential ?
I hope you found this informative, and I would sugges that you download or
upgrade to the latest version.
Ralf Nieuwenhuijsen
nieuwen at xs4all.nl
