From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from discorde.inria.fr (discorde.inria.fr [192.93.2.38]) by yquem.inria.fr (Postfix) with ESMTP id 265ADBC0B for ; Tue, 16 Jan 2007 21:14:08 +0100 (CET) Received: from mail.enyo.de (mail.enyo.de [212.9.189.167]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l0GKE6hM013287 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 16 Jan 2007 21:14:07 +0100 Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1H6ugz-0007S9-6N; Tue, 16 Jan 2007 21:14:01 +0100 Received: from fw by deneb.enyo.de with local (Exim 4.63) (envelope-from ) id 1H6ugj-0005KY-Pz; Tue, 16 Jan 2007 21:13:45 +0100 From: Florian Weimer To: Edgar Friendly Cc: Christophe TROESTLER , caml-list@yquem.inria.fr Subject: Re: [Caml-list] Ocaml compiler features References: <45A87011.8080203@gmail.com> <20070115103556.GB12311@furbychan.cocan.org> <45AC60CB.4070408@gmail.com> <20070116.065515.246091320.Christophe.Troestler@umh.ac.be> <45AD10BF.60606@gmail.com> Date: Tue, 16 Jan 2007 21:13:45 +0100 In-Reply-To: <45AD10BF.60606@gmail.com> (Edgar Friendly's message of "Tue, 16 Jan 2007 11:51:59 -0600") Message-ID: <87d55eybk6.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at discorde with ID 45AD320E.005 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; ocaml:01 compiler:01 compiler:01 edgar:98 stone:98 abstract:01 caml-list:01 implementors:02 florian:03 warnings:03 indentation:04 enforce:05 style:93 written:07 quite:07 * Edgar Friendly: > As for changing the C language, 1: it's already written in stone Not quite true. After all, you don't actually use the language in the abstract, but there's a real compiler, which can issue as many warnings as its implementors deemed reasonable. For instance, it makes perfect sense to enforce certain style guidelines at the compiler level (proper indentation, mandatory braces except for "else if" etc.)