Actually, I didn't suggest identifier should replace word. I said any that
looks like an identifier. Note that perldata in its second paragraph already defines how identifiers look like.
but I worry that identifier might have limitations that would not be appropriate.
Don't. Think about it. When parsing, on encountering a possible 'bare word', the parser doesn't look ahead and say "hmmm, let me see, if the token following this bare word thingy isn't a fat comma, I'm going to parse it as an identifier, because it's got to be a subroutine or a file/dir handle, but if it isn't followed by a fat comma, I'm going to accept something slightly different". No, the parser is going to parse something that may be a valid identifier. Then it looks whether it's in autoquoting context (next token is a fat comma, or we're indexing in a hash and the next token is a close brace), in which case the thing just parsed is a string, otherwise, it is indeed an identifier (subroutine, file/dir handle).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.