I'd like to propose a change to Unicon that, while minor, would
have the major impact of breaking backward compatibility with
Icon. However, I believe that the number of Icon programs that
use the feature in question is actually *quite* small.
Because of the impact, I don't really think this proposal will
fly, but thought it would be worth some discussion. Feel free
to disagree!
Oh, right - the proposal: drop the string continuation semantics
of literal strings in Unicon.
That is, disallow the following in Unicon programs:
procedure main()
write("hi _
there")
end
Why?
(1) There's an alternative that's cleaner:
procedure main()
write(" hi " ||
"there")
end
(2) It's a syntactic pit when trying to write code that reads Unicon
expressions - as near as I can tell it's the *only* language feature
that requires line read-ahead in the tokenizing phase (there is
still line read ahead in the parsing phase, but that's pervasive and
unavoidable).
Comments? Not worth worrying about?
--
Steve Wampler <[EMAIL PROTECTED]>
National Solar Observatory
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
