in reply to Why has perl never been a compiled language...

eval is the problem that comes to my mind. Because you can build and execute arbitrary bits of code, you need something that can parse perl. I imagine that s///e would also be a problem. If the code that's generated is moderately complex, you would likely have bugs.

Here's an interesting bit of explanation of the current compiler status.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

  • Comment on (Ovid) Re: Why has perl never been a compiled language...

Replies are listed 'Best First'.
Re: (Ovid) Re: Why has perl never been a compiled language...
by diotalevi (Canon) on May 21, 2003 at 17:36 UTC

    That's /ee. A single /e is handled at compile-time and is sort of like an block-eval. More than one /e has the first part handled normally but then the result is passed into string-eval which involves the compiler at runtime ... etc.