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
use Perl Log In
gav (2710)
gav
(email not shown publicly)
http://www.estey.com/
AOL IM: flufflegavin (Add Buddy, Send Message)
Hacker in NYC.
(email not shown publicly)
http://www.estey.com/
AOL IM: flufflegavin (Add Buddy, Send Message)
Hacker in NYC.
Monday August 05, 2002
10:57 AM
odd little thing
I was tidying up a script for a client that was previously working fine and noticed it was really, really slow. Processing a 600k file was taking about 30 seconds. This seemed big odd as the module that was doing the grunt work was something I've used for several projects and handles 15meg files without complaint. I thought the best thing to do would be top copy it over to my linux box and attack it with Devel::DProf and see what's up.
The script was using Config::Ini which no longer seems to be on CPAN which is a bit confusing. I commented out the code that used that and hardcoded the values I wanted. The script ran in about 2 seconds.
I guess I'd better look at finding a new module to handle INI files
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Randal did a column on INI file parsing.. (Score:1)
Re:Randal did a column on INI file parsing.. (Score:1)
I think there should be one called 'Randal Already Did It' :)