The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Thu, 23 Jan 2003 10:47:20 +0100
Local: Thurs, Jan 23 2003 4:47 am
Subject: Re: Transferring control between code segments, eval, and suchlike things
Benjamin Stuhl wrote: IMHO this is a big waste of memory - and running this page aligned code > At 03:00 PM 1/22/2003 -0500, you wrote: > ... Although, > all this would seem to suggest that we'd need/want a special-purpose > allocator for bytecode segments, since every sub has to fit within > precisely > one segment (and I know _I'd_ like to keep bytecode segments on their > own memory pages, to e.g. maximize sharing on fork()). JITted doesn't buy anything. >> Design Edict #7: the compreg opcode will execute the compiled code, Precompiled PBC and eval is a PITA. This issue seems to imply some extra >> calling in with parrot's calling conventions. If it should return >> something, then it had darned well better build it and return it. > How does this play with > eval 'sub bar { change_foo(); } BEGIN { bar(); } (...stuff that depends > ? The semantics of BEGIN{} would seem to require that bar be installed parsing during load time and setting up symbols. I dunno yet, how to handle this. leo You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||