On Sat, Mar 15, 2008 at 09:00:27AM -0700, Matisse Enzer wrote:
> On Mar 15, 2008, at 6:45 AM, David Cantrell wrote:
> >On Fri, Mar 14, 2008 at 12:20:40PM -0700, Matisse Enzer wrote:
> >>What are other good reasons to have package declarations match file
> >>paths?
> >Because it's what everyone does and there are no good reasons to *not*
> >do it.
> With all due respect David, I don't think that's a good answer
That's OK, you're allowed to be wrong :-)
> I'm trying to give some good reasons to some intelligent folks, who are
> actually asking to understand the underlying reasons for this "best
> practice." I think the "least surprise" answer couple with the
> import() issue are better answers.
"It's what everyone else does" *is* the principle of least surprise.
> (Personally I virtually never use
> import() but it's still a factor.)
You use it whenever you use strict:
$ perl -e 'use strict; $h = "moo"'
Global symbol "$h" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.
$
and now, not calling import():
$ perl -e 'use strict (); $h = "moo"'
$
--
David Cantrell | top google result for "topless karaoke murders"
You are so cynical. And by "cynical", of course, I mean "correct".
-- Kurt Starsinic
