[nem-en] [RFC] type parens

[Michal Moskal]

On Fri, Sep 24, 2004 at 04:12:49PM +0000, Kojo Adams wrote:
> Hi all,
> 
> 
> >Now there is a problem with Hashtable<int,string> kind of things, since
> >the <> operators are used both as parens and common operators. There is
> >no easy way to distinguish between f(x < foo, y > bar) and x<foo,y>.
> Rhys Weatherly mentions how he fixed these issues in cscc at 
> http://mailserver.di.unipi.it/pipermail/dotnet-sscli/msg00184.html.

This is somewhat related, but different issue. This is about yacc
parsers. We're not going to use yacc -- there will be two level, hand
written parser. However the second part is going to be parametrized with
user-defined rules, that will hopefully provide more flexible ways of
extending the parser, then the current solutions.

As a side note, the solution Rhys choose seems quite hackish, and is of
the kind I would like to avoid in Nemerle.

> If the syntax has to be changed, I vote the Hashtable<<int, string>> option 
> better than any of the others mentioned. They are not too much of a 
> depature from the c# syntax, and new users can learn it easily.

Maybe you're underestimating the power of new users ;-) It shouldn't be
hard to grasp the idea of changing <> to [].

-- 
: Michal Moskal :: http://www.kernel.pl/~malekith :: GCS !tv h e>+++ b++
: ::: Logic is a nice contrast to the Real World. :: UL++++$ C++ E--- a?