From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by pauillac.inria.fr; Mon, 30 May 94 11:48:00 +0200
Received: from margaux.inria.fr by pauillac.inria.fr; Sat, 28 May 94 13:05:37 +0200
Received: from pauillac.inria.fr by margaux.inria.fr, Sat, 28 May 1994 13:05:36 +0200
Received: from localhost.inria.fr by pauillac.inria.fr; Sat, 28 May 94 13:05:35 +0200
To: Christophe Raffalli <cr@dcs.ed.ac.uk>
Cc: Judicael.Courant@lip.ens-lyon.fr, caml-list@margaux.inria.fr
Subject: Re: Irrelevant variables in patterns 
In-Reply-To: Your message of Sat, 28 May 1994 12:01:55 -0000.
             <13595.9405281101@colonsay.dcs.ed.ac.uk> 
Date: Sat, 28 May 1994 13:05:35 +0200
Message-Id: <29612.770123135@pauillac.inria.fr>
From: Chet Murthy <murthy@pauillac.inria.fr>
Sender: weis@pauillac.inria.fr


>>>>> On Sat, 28 May 1994 12:01:55 -0000, Christophe Raffalli <cr@dcs.ed.ac.uk> said:

	CR> I understand your "point de vue". But then to catch the
	CR> mispelling of an exception, the only solution I can see is a
	CR> different syntax for constructors and variables at least in
	CR> pattern (a quote in front of the constructeur in pattern
	CR> only).

Yes - Daniel de Rauglaudre suggests (and I agree) that we capitalize
constructors, and not capitalize variables.

Another simple solution is to disallow variables in case/match/try
which do not actually occur in the body.  If you really want to have
such variables around, then put an underscore in front of the name.

--chet--