Short, succint constant names are short, easier to get right, more meaningful. Otherwise, don't sweat it.
What if you mispell your constant name, ITE_NOT_FOUND, and since it's only used once, or you cut-and-paste the two or three places it is used, you don't detect the typo? Maybe you should spell-check your document.
What language are your constants? Other than capitalization and s/ /_/g, they are identical to the 'English' constants.
It's kind of you to be concerned about others, but non-programming users don't care about what's inside your program. To a Korean grandmother, the text of your script is as comprehensible as the binary of a compiled program. As far as she's concerned, neither uses the alphabet ... our alphabet being meaningless squiggles to her, just as her's is to us. As for non-English programmers, they are already forcecd to use English, whether they use C, Java, Python or Perl: if, open, use.
As a Canadian, I get peeved by US-oriented software standards that make me mispell words. When I use JavaScript or generate HTML in code, I sometimes write things like:
<body bgcolor="$bgcolour">
Luckily, some weird bug will usually distrtact me before I startt fuming.
In reply to Re: Locale::Maketext Lexicon Opinions
by TomDLux
in thread Locale::Maketext Lexicon Opinions
by jk2addict
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |