From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id XAA20260; Mon, 4 Feb 2002 23:53:50 +0100 (MET) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id XAA19228 for ; Mon, 4 Feb 2002 23:53:44 +0100 (MET) Received: from plinky.bolt-action.com (node-d8e9cca3.powerinter.net [216.233.204.163]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id g14MrgX28106 for ; Mon, 4 Feb 2002 23:53:43 +0100 (MET) Received: from checkerlap.d6.com (node-d8e9cca2.powerinter.net [216.233.204.162]) by plinky.bolt-action.com (8.11.6/8.9.3) with ESMTP id g14MtdW10834; Mon, 4 Feb 2002 14:55:45 -0800 Message-Id: <4.3.2.7.2.20020204144529.037923f0@arda.pair.com> X-Sender: checker@arda.pair.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 04 Feb 2002 14:52:29 -0800 To: Markus Mottl , Mattias Waldau From: Chris Hecker Subject: Re: [Caml-list] syntax change (was: camlp4o problem) Cc: caml-list@inria.fr In-Reply-To: <20020204201140.GA1705@fichte.ai.univie.ac.at> References: <004b01c1ada9$ae1d0420$765da8c0@gateway> <20020204180136.F2338@verdot.inria.fr> <004b01c1ada9$ae1d0420$765da8c0@gateway> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk >This will probably not happen: there is just not enough incentive to >learn a new syntax which is unlikely to become widespread - because it >is non-standard. I agree with this. I think it'll have to be a top-down decision or it won't happen for real. I (7660 lines of caml and going up quickly in my project) would make a major syntax change if I thought it was an investment in getting things "right" for moving forward. I'd like it to happen sooner rather than later, if it was going to happen. I've been tempted to try the revised syntax, but I didn't want to start mixing multiple syntaxes in a single project, and I would rather use the "standard" (whichever it is, and no definition of "standard" offered or wanted) just to make life easier. I think you rarely get a chance to change major things, and so you should take the opportunity before it's too late. I would support such a change if the team wanted to do it. I don't think they should do it lightly, obviously, but I also don't think they should be terrified of a change like this either. Decide what's best for the future of caml, weighing user pain (but not overly strongly) and cleanliness benefit, and make a decision. Chris ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr