Re: routine_id evaluation
- Posted by Kat <gertie at PELL.NET> Dec 02, 2000
- 561 views
On 2 Dec 2000, at 16:10, Derek Parnell wrote: > ----- Original Message ----- > From: "Robert Craig" <rds at RAPIDEUPHORIA.COM> > > > Derek Parnell writes: > > > I don't suppose you'd consider allowing routine_id > > > to be evaluated at run-time rather than at "compile" time? > > > > It *is* evaluated at run-time. > > However, it will only find routines that are defined > > earlier than the place where you call routine_id(). > > Robert, did you get out of the wrong side of bed this morning. Please don't > play semantic games. You know that I already know how it works now, and you > know perfectly well what it is that I'm asking for! > > Of course its currently done at run-time because its an interpreted > language. With an interpreted language, everything is run-time! It seems > that what you are implying is the Euphoria evaluates the parameter during the > syntax checking stage of the interpretation rather than the execution stage of > the interpretation. `cuse me, but if Eu is doing a pass on the script before executing, why is there a need for routine_id() at all? Simply do not abort the pass that finds unknown routine calls untill the end of the pass, where you can see if any calls are still unknown. This would solve the problem Derek demonstrates, no? Kat