Talk:Abbreviations, easy: Difference between revisions
→Incorrect example output?: new section
m (→Need some clarifications: added an explanation concerning an interrupted two-part deletion.) |
(→Incorrect example output?: new section) |
||
Line 57:
:: Yes, but the spec doesn't specify a '''blank''' string for output. The question isn't about '''blank''' strings. I never even mentioned a '''blank''' string. The spec say return a '''null''' string. The term '''null''' can be interpreted in many different ways.... Never mind. I'm not going to repeat my whole explanation and inquiry. --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 10:18, 19 September 2017 (UTC)
== Incorrect example output? ==
Why does <code>put</code> return <code>PUT</code> instead of <code>*error*</code>? One of the stipulations is "if there isn't any lowercase letters in the word in the command table, then there isn't an abbreviation permitted." <code>PUT</code> and <code>PUTD</code> are the only commands that begin with <code>put</code> but they are both all-caps, so an abbreviation should not be permitted.
| |||