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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Why? (Score:2)
The docs make the excuse that loading time modules takes 3-4MB (only true for DateTime - try something lighter like Date::Class or Time::Piece), but for *::Tiny to do anything useful it looks like you'd have to do that anyway.
I (for obvious reasons) totally disagree with the flamebait in your docs about how DateTime.pm is the
Re: (Score:1)
What I found was that quite a significant amount of work was having to be done just to create the DateTime objects, far more than I was comfortable with.
And yet the data did not require that level of rigour, I wasn't going to be doing anything with the dates, just holding them in memory, possibly converting to a
Re: (Score:2)
I guess I'm lucky enough to have never really needed that much comprehensiveness. 4MB just to load one damn perl module (never mind the hassle of installing the thing) is just asking too much.
Re: (Score:1)
The only problem was on Windows, and the DateTime guys have fixed that now.
But yes, it is expensive. Which is why the Tiny modules exist.
And while I have your attention, any chance of getting some small releases of the modules you have commit on (that I mentioned a few posts ago).
The bugs are tiny things, but it would help us out a LOT to have some of your high profile modules working on Windows.
Re: (Score:2)
Re: (Score:1)
The specific bugs causing the problem are on win32.perl.org
http://win32.perl.org/wiki/index.php?title=Problem_Modules [perl.org]
Re:Why? (Score:2)
I'll try and get around to DBD::SQLite later today.
Reply to This
Parent
Re: (Score:1)
Just double checked and not working here either.
I'm CC'ing you on the particular failure.