One of the other threads I mentioned (tr doesn't *really* use a list), as you
can tell from the title, shows how "list" is used in the
Perl documentation to talk about at least one more thing
than the two that you list. This appears to have caused at
least a little confusion.
I'd list all of the ways that "list" is used within the
Perl documentation, but the thought of compiling such a
list makes me listless. ;)
I think that being able to talk about a "list" within a
given documentation context is helpful in making the
documentation easy to read. So no, I don't think changing
"list" to "list literal" or "list value" everywhere would
be an improvement.
There are some places in the documentation that
could be made more clear by being explicit about what is
meant by "list" in that section.
But I think the important thing is to get people to realize
that they have to figure out what is meant by "list"
in each context. And that is what I am trying to do.
(but my friends call me "Tye")
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||