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.
map and grep (Score:1)
I think these two are among the most beautiful operators that exists in Perl and deserve some nice examples.
Envy! (Score:2)
Congrats. And that's a great first example. There's so much hidden away behind an interface that's intuitive (though I think the abstraction is marred by the lack of a thrown exception). I think 'use Fatal' would also be fantastic. It seems like a simple example, but it's really beautiful (to me) in what it does.
import vs explicit importing (Score:1)
use LWP::Simple 'get'What happened to the mantra from Exporter.pod?
"Do not export anything else by default without a good reason!
Re: (Score:2)
Oh, its intentions are good. Its there to make authors think and to avoid modules like POSIX which export nearly everything. So often people only hear the "do not export anything by default" and miss the "without a good reason" part.
If your module doesn't do anything useful but provide functions, go ahead and export some useful defaults. The user's going to have to import stuff anyway, give them a leg up. Why? Choice. Specifically the user's.
Any module which exports by default can be
Re: (Score:1)
Personally, I have mixed feelings about it. Some default exports can be handy and look clean. However, I like to grep my code for a function name and be able to figure out where it came from.
OO code tends to be traceable to the object construction. But with with procedural code, if there's no explicit export, it is more difficult to track down where a function comes from, and that can slow me down. (Yes, I know there are modules and techniqu
Re: (Score:2)
The wonderful thing is as a user of the module you always have that option no matter what the module author chooses to do.