comment on

There is nothing that says that your constant subs have to have all upper case names.

My personal preference has evolved to be mixed case names starting with an upper case letter. This avoids the conflict you describe, and (in my schema), distinguishes constant subs from other subs which are mixed case but start with a lower case letter.

I also find it infinitely preferable to so called Readonly variables--which is just a nonsense IMO. (Ie. variables that don't). Constant subs also allow Perl to perform optimisations that are not possible with 'Readonly variables'; and they don't carry that modules overheads.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Constant names come into conflict with Perl style? by BrowserUk
in thread Constant names come into conflict with Perl style? by dmitri

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks