Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Wow, 20 answers. Very thoroough -- thanks, Dan :)

    So, which was the "the answer is X, but you're really asking about Y question?"



  • Hey, how come I don't see BeOS listed as a "showstopper" platform? :-P

    Ah, well. I'm still waiting on socket support.

    • D'oh! I knew I forgot something. We'll get it on the list... right after we add in TOPS-20 and RSTS/E. ;-P
  • 2. All dead objects with active destructors will eventually have their destructors called

    Quick question related to this: Will memory reclaimed from garbage-collected variables be retained by Parrot the way Perl 5 retains memory, or could memory eventually be released back to the OS? I could see the latter helping a lot compared to certain mod_perl applications I'm familiar with.

    • by Elian (119) on 2002.05.07 13:23 (#8102) Homepage Journal
      When a memory pool is empty (which happens with some frequency because we've got a copying garbage collector) the empty pool is freed back to the system. Whether this actually releases memory back to the system depends on your OS and the method Parrot uses on your platform to allocate and deallocate its large chunks of memory.

      Now, having been appropriately dodgy...

      Odds are you'll see memory get released on pretty much any platform you can name. The allocation and deallocation code for large chunks is in a single, small place, and having a build-time option on the memory allocator's a simple enough thing if its even needed. (Some systems are clever when we allocate large chunks, and do it in a way that lets them be released back into the free memory pool)