On Wed, May 26, 2010 at 5:55 PM, Attila Szegedi <[email protected]> wrote:
> On 2010.05.26., at 18:22, Rémi Forax wrote: > > > In the same time, users don't want to understand parsers/grammar > limitations. > > Users want things like optional semicolon like in Javascript or Groovy, > > Optional semicolon is exactly the main bane of anyone who wants to write a > conventional grammar for JavaScript - newline is either whitespace, or > significant, depending on context. Bah :-) > > It's always like that - implementers have to work hard to make something > easy and convenient for users. > In my experience "optional" semicolons (see also Perl's optional parens) can't really be made 100% optional in the event of interacting with other language features, and those edge cases seem to come more often than expected. Then lots of users get confused, and it leads to cargo-culting of language syntax. I read a very good post recently about the edge cases of the optional syntax features of various languages and why they aren't always. Now, if I can only find it again... Ben -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
