Re: Location of 'use' statements

[perrin]

Number 3 of course! Putting anything before your package statement is just wierd, and pragmas and inheritance are more important than external libraries. I would consider "use constant" a totally different kind of thing and put it after everything else with a blank line above it. (Actually, I would just not use that annoying thing, but that's a different story.)

[demerphq]

(Actually, I would just not use that annoying thing, but that's a different story.)

I for one would like to hear that story. I don't use them often, primarily for real constants (like OS constants and the like) and things like DEBUG. But I'm curious if theres some trap or zap that I havent quite fallen into that I aught to know about?

---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}

[perrin]

The problem with "use constant" is that the constants are implemented as subroutines. This means that they break (silently) if you try to use them as hash keys, in double-quoted strings, or any other place where barewords are not interpreted as sub calls.

If you use global variables instead, everyone knows what they are and you avoid these bugs which tend to catch every user of constant at least once.

[demerphq]

This means that they break (silently) if you try to use them as hash keys, in double-quoted strings, or any other place where barewords are not interpreted as sub calls.

Hmm. *grin* I can't recall being bitten by those things. I've used constants for array indexes on occasion, but never hash indexes. But its good to keep in mind. Thanks.


---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}