Re: Comments on ORAC

new topic     » goto parent     » topic index » view thread      » older message » newer message

Bernie Ryan wrote:
> 
> CChris wrote:
> > 
> > If there is a way - whichever it is - to tell from an id what it refers to -
> > function vs procedure, indirect Eu vs external - then there would be no need
> > for c_proc() vs call_proc(), since any of them would do the right thing. So
> > the change would simplify the language.
> > Having the index in the indirect call table being different from the id
> > returned
> > to programmer isn't much of a problem, since the conversion would be fast -
> > either shifting or anding -.
> > 
> 
> CChris:
> 
> If Euphoria did multipass parsing; then allot of routine_id complications
> 
> could be handle internally by the interpeter.
> 
> That would go along way to simplify the language.
> 
> Bernie
> 
> My files in archive:
> WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API 
> 
> Can be downloaded here:
> <a
> href="http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan">http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan</a>

True. However, this leads to non optimal use of memory (too many cache misses).
I didn't test what the performance penalty would be, but I'm afraid it would be
noticeable.
Fortunately, this is not needed. You may check the modified interpreter which
ships with Orac to see how to handle forward references, and avoid 80-90% of all
call_func/call_proc/routine_id calls altogether.

CChris

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu