Dan Sugalski <[EMAIL PROTECTED]> writes: > From a language perspective, I have a scheme to allow us to yank all the > cruft (sockets, shm, messages, localtime...) out into separate libraries, > yet pull them in on demand without needing a use. a la dbmopen in perl5? -- Piers
- Re: date interface (was Re: perl6 requirements, on boo... J. David Blackstone
- Re: date interface (was Re: perl6 requirements, o... Dan Sugalski
- Re: date interface (was Re: perl6 requirement... Simon Cozens
- Re: date interface (was Re: perl6 require... Dan Sugalski
- Re: date interface (was Re: perl6 req... Simon Cozens
- Re: date interface (was Re: perl... Dan Sugalski
- Stuff in core (was Re: date inte... Simon Cozens
- Re: Stuff in core (was Re: date ... Dan Sugalski
- Re: Stuff in core (was Re: date ... Tim Bunce
- Re: Stuff in core (was Re: date ... Tim Bunce
- Re: Stuff in core (was Re: date ... Piers Cawley
- Re: Stuff in core (was Re: date ... Dan Sugalski
- Re: date interface (was Re: perl6 require... Nick Ing-Simmons
- Re: date interface (was Re: perl6 requirement... J. David Blackstone
- Re: date interface (was Re: perl6 require... Bryan C . Warnock
- Memory Footprint of Perl System Calls (wa... mooring
- Re: date interface (was Re: perl6 requirements, o... Nathan Torkington
- Re: date interface (was Re: perl6 requirement... Chaim Frenkel
- Re: date interface (was Re: perl6 require... Dan Sugalski
- Re: date interface (was Re: perl6 req... Chaim Frenkel
- Re: date interface (was Re: perl6 requirements, o... Damian Conway