From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 436667EE8B for ; Fri, 22 Mar 2013 10:16:39 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.161; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.161 as permitted sender) identity=mailfrom; client-ip=134.160.33.161; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.161 as permitted sender) identity=helo; client-ip=134.160.33.161; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="postmaster@postman.riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai8BAJkgTFGGoCGhmWdsb2JhbABDhROuN5I1gXUOAQEBAQETCwcUKIIkAQEEATg2CgYLCxgJBBIPCQMCAQIBMxITBgIBAQ6HcAMJBgy4DgOJZY8ZFoMqA4h1jW+BH4Rejh8 X-IPAS-Result: Ai8BAJkgTFGGoCGhmWdsb2JhbABDhROuN5I1gXUOAQEBAQETCwcUKIIkAQEEATg2CgYLCxgJBBIPCQMCAQIBMxITBgIBAQ6HcAMJBgy4DgOJZY8ZFoMqA4h1jW+BH4Rejh8 X-IronPort-AV: E=Sophos;i="4.84,891,1355094000"; d="scan'208";a="8795363" Received: from postman1.riken.jp (HELO postman.riken.jp) ([134.160.33.161]) by mail2-smtp-roc.national.inria.fr with ESMTP; 22 Mar 2013 10:16:38 +0100 Received: from postman.riken.jp (postman1.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id 1CA6032C030C for ; Fri, 22 Mar 2013 18:16:35 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 8300632A0047 for ; Fri, 22 Mar 2013 18:16:34 +0900 (JST) Message-ID: <514C2172.7090609@riken.jp> Date: Fri, 22 Mar 2013 18:16:34 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: caml-list@inria.fr References: <514C1E1B.9050907@riken.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.22.90326 Subject: Re: [Caml-list] Warning 20: Unused function argument On 03/22/2013 06:05 PM, Gabriel Scherer wrote: > My own guess (pure speculation) as to why this difference is that > enabling it by default would have raised too many warnings on existing > code, in particular breaking code of people sadly using a "all enabled > warnings are errors" discipline (don't!), while unused let-bound > variables where much less frequent in existing code. OCaml is not lazy, so that's not very smart if some of my functions have unused arguments... I have to fix my code. :( > On Fri, Mar 22, 2013 at 10:02 AM, Francois Berenger wrote: >> Hello, >> >> I understand it is turned off by default. >> >> I am a bit surprised as it is as important >> to me as an unused variable, which triggers a warning >> by default. >> >> Regards, >> F. >> >> -- >> Caml-list mailing list. Subscription management and archives: >> https://sympa.inria.fr/sympa/arc/caml-list >> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners >> Bug reports: http://caml.inria.fr/bin/caml-bugs >