Talk:Empty string: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
Line 16:
:::Certainly. But <code>nil.to_s</code> has syntax which is not the standard syntax for representing an arbitrary string. But perhaps your objection is that the syntax involved is not dedicated to the purpose of representing empty strings? It's true that the method invocation syntax behind <code>nil.to_s</code> is very general and that <code>'arbitrary string'.to_s</code> can be used to represent an arbitrary string. --[[User:Rdm|Rdm]] 19:58, 6 July 2011 (UTC)
::::I think Kevin Reid's objection is valid, as none of the examples here so far provided a ''syntax'' dedicated to dealing with an empty string; <code>nil.to_s</code> in a sense is still showing the ''semantics'' about equivenlance between nil and empty string. It probably wouldn't do any harm to leave the "syntax" wording alone, but strictly speaking it shouldn't be there. --[[User:Ledrug|Ledrug]] 01:28, 8 July 2011 (UTC)
:::::How about http://www.snobol4.org/docs/burks/tutorial/ch4.htm? Here, an empty replacement field is treated as an empty string. (Note that in another context in snobol, blank is a concatenation operator.)
:::::<lang bash>$ FOO='5'; FOO=''; echo $FOO
$ FOO='5'; FOO=; echo $FOO</lang> --[[User:Rdm|Rdm]] 01:40, 8 July 2011 (UTC)
::The possible minor rewording of the task description will not affect the task itself. Is there any reason that we can not promote this to task? [[User:Markhobley|Markhobley]] 16:42, 7 July 2011 (UTC)
| |||