> > Why does string C<eval> have to screw everything up? Nathan Torkington <[EMAIL PROTECTED]> wrote: > It doesn't. String eval is the escape hatch from a language that can't do > what you want it to do. As such it's okay for it to be slow--consider it > incentive to fix the language :-) The runtime system should be able to > load the compilation system and say "turn this SV into a CV in this > lexical scope," and then call the CV. Whether or not it is slow is not my concern. My concern is *can* we support it on architectures that don't have a native C compiler (i.e., the JVM). I think that's the first and foremost concern with eval($string) (and hence, the parser). Slow things can usually be made faster, but "can't get there from here" is often hard to solve. -- Bradley M. Kuhn - http://www.ebb.org/bkuhn
- Supporting architectures without n... Bradley M. Kuhn
- Re: Supporting architectures w... Jarkko Hietaniemi
- Re: Supporting architectures w... Bradley M. Kuhn
- Re: Supporting architectures w... Adam Turoff
- Re: Supporting architectures w... Bradley M. Kuhn
- Re: Supporting architectures w... Joshua N Pritikin
- Re: Supporting architectures w... Jarkko Hietaniemi
- Re: Supporting architectures w... Bradley M. Kuhn
- Re: Meta-design Dan Sugalski
- Re: Meta-design Simon Cozens
- Re: Meta-design Bradley M. Kuhn
- Re: Meta-design Simon Cozens
- Let's not be C-specific even if we use C (w... Bradley M. Kuhn
- Re: Let's not be C-specific even if we ... Simon Cozens
- Re: Let's not be C-specific even if we ... Adam Turoff
- OO AV/HV's and tie (was Re: Meta-design) Nathan Wiger
- Re: OO AV/HV's and tie (was Re: Meta-design) Simon Cozens
- Re: OO AV/HV's and tie (was Re: Meta-design) Dan Sugalski
- Re: OO AV/HV's and tie (was Re: Meta-design... Simon Cozens
- Re: OO AV/HV's and tie (was Re: Meta-de... Dan Sugalski
- Re: OO AV/HV's and tie (was Re: Meta-design) Nathan Wiger