On Tue, Jun 28, 2005 at 10:21:20PM +0100, Dave Mitchell wrote: > On Tue, Jun 28, 2005 at 11:24:59AM -0700, Michael G Schwern wrote: > > Its the principle of the thing. Also, not initializing $Verbose and > > $MaxEvalLen seems going a little overboard espcially when it violates the > > docs. Finally I threw in "our" onto the globals so one can turn on strict > > during testing. And a version bump. > > your patch increases final memory usage by 460 bytes, and total mallocs by > 1200 bytes.
Hopefully that's just for informational purposes and you're not actually proposing rejecting the patch to save 460 bytes. > > The next target for "use less 'memory'" should probably be Exporter. > > Exporter's already pretty tight. Exporter will load Exporter::Heavy if it sees "&foo" in its import list. It will not for "foo". This is because any work for symbols goes off into Exporter::Heavy. This always struck me as being a bit unnecessary. A bunch of modules use &foo style exports. It would be nice if Exporter wouldn't do this. The obvious thing to do is strip off the & before processing but the extreme memory saving code style in Exporter makes this kind of difficult. I'll take a whack at it. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern 'All anyone gets in a mirror is themselves,' she said. 'But what you gets in a good gumbo is everything.' -- "Witches Abroad" by Terry Prachett
