|
|
|
|
|
|
by bluefirebrand
1867 days ago
|
|
|
I can see where you're coming from, it does read like "MUST support up to 100 characters (and MAY support more of you choose). But honestly I think it's a bad practice to build the "may" part, because it's not explicit. The person who wrote the spec just as easily could have intended it to be "MUST support up to 100 (and may not go over 100)". So by not setting a bound you're gambling with your implementation being rejected, but setting a bound at 100 satisfies both possible "implied clauses" of the requirement and should not be rejected. |
|
|