--- Dave Mitchell <[EMAIL PROTECTED]> wrote: > On Thu, Jan 23, 2003 at 09:21:45PM +0100, Juergen Boemmels wrote: > > My current idea for the in memory format of the bytecode is this: > > I would strongly urge any file-based byte-code format to arranged > in such a way that it (or most of it) can simply be mmap-ed in (RO), > analogously to executables. > > This means that a Perl server that relies on a lot of modules, and > which > forks for each connection (imagine a Perl-based web server), doesn't > consume acres of swap space just to have an in-memory image per Perl > process, of all the modules.
sounds good. could that be seen as similar to shared memory communication with the compile, via mem-mapped file interfaces? mike > This is a real problem that's hitting me hard with Perl 5 in my day > job. > > Dave. > > -- > Any [programming] language that doesn't occasionally surprise the > novice will pay for it by continually surprising the expert. > - Larry Wall ===== James Michael DuPont http://introspector.sourceforge.net/ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
