Naming conventions: Difference between revisions
Content added Content deleted
(→{{header|Factor}}: clarify a bit) |
(→{{header|Factor}}: change some awkward wording) |
||
| Line 501: | Line 501: | ||
Words are <code>named-with-dashes</code> instead of <code>named_with_underscores</code> or <code>namedWithCamelCase</code>. We tend to avoid abbreviating names. Since we typically don't name throwaway values, this improves clarity. Parsing words are <code>NAMED-LIKE-THIS:</code> so words that perform parse time look-ahead can be easily identified. |
Words are <code>named-with-dashes</code> instead of <code>named_with_underscores</code> or <code>namedWithCamelCase</code>. We tend to avoid abbreviating names. Since we typically don't name throwaway values, this improves clarity. Parsing words are <code>NAMED-LIKE-THIS:</code> so words that perform parse time look-ahead can be easily identified. |
||
Since words can be named anything as long as they don't parse as a number or a string, word names follow an expressive mnemonic system, outlined below. This is not enforced in any way, but encouraged as a way to |
Since words can be named anything as long as they don't parse as a number or a string, word names follow an expressive mnemonic system, outlined below. This is not enforced in any way, but encouraged as a way to convey intent. |
||
{| class="wikitable" |
{| class="wikitable" |
||