From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 951F97EE51 for ; Thu, 18 Apr 2013 18:40:34 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of bills@emu-bark.com) identity=pra; client-ip=173.201.192.108; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bills@emu-bark.com"; x-sender="bills@emu-bark.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of bills@emu-bark.com) identity=mailfrom; client-ip=173.201.192.108; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bills@emu-bark.com"; x-sender="bills@emu-bark.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@p3plsmtpa06-07.prod.phx3.secureserver.net) identity=helo; client-ip=173.201.192.108; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bills@emu-bark.com"; x-sender="postmaster@p3plsmtpa06-07.prod.phx3.secureserver.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgADAAghcFGtycBsemdsb2JhbABQgkJ6iQ+4URYOAQEJDQkJESuCHwEBBHkGGgEcFhgDAgECAT8MDQgBAYgKBp0/oT6SZgOYKoRkjjQ X-IPAS-Result: AgADAAghcFGtycBsemdsb2JhbABQgkJ6iQ+4URYOAQEJDQkJESuCHwEBBHkGGgEcFhgDAgECAT8MDQgBAYgKBp0/oT6SZgOYKoRkjjQ X-IronPort-AV: E=Sophos;i="4.87,502,1363129200"; d="scan'208,217";a="11458929" Received: from p3plsmtpa06-07.prod.phx3.secureserver.net ([173.201.192.108]) by mail3-smtp-sop.national.inria.fr with ESMTP; 18 Apr 2013 18:40:32 +0200 Received: from [192.168.0.2] ([173.26.186.224]) by p3plsmtpa06-07.prod.phx3.secureserver.net with id RUgS1l00M4qv3b901UgTos; Thu, 18 Apr 2013 09:40:28 -0700 Message-ID: <51702200.1050806@emu-bark.com> Date: Thu, 18 Apr 2013 12:40:32 -0400 From: William Smith User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Caml-list Content-Type: multipart/alternative; boundary="------------080809000804000808080907" Subject: [Caml-list] modified error messages for ocamlc This is a multi-part message in MIME format. --------------080809000804000808080907 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit > > File "multilineError.ml", line 2, character 0-line 4, character 1: > This added info is great, but if you change the format, then please take > advantage of this opportunity to make use a more standard format so that > other tools can recognize those messages without extra work. > E.g: > multilineError.ml:2.0-4.1: Warning 8: this pattern-matching is not exhaustive. > Stefan This is harder than it looks because there are about a dozen places in the code where OCaml creates error messages. They're spread out amongst all of the tools. I believe I found them all, but each one requires careful work to avoid breaking things. So far, I've only changed the one in ocamlc. After finding them, I'll also need to learn how to trigger each of them to even test the change. That's why I don't want to do it unless it's really useful to people. I don't use emacs right now so I don't know how to test that part of the system. Will using the standard Gnu error format be ok with what Daniel Bünzli was concerned about? Bill --------------080809000804000808080907 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

> File "multilineError.ml", line 2, character 0-line 4, character 1:

> This added info is great, but if you change the format, then please take
> advantage of this opportunity to make use a more standard format so that
> other tools can recognize those messages without extra work.

> E.g:

> multilineError.ml:2.0-4.1: Warning 8: this pattern-matching is not exhaustive.


>        Stefan

This is harder than it looks because there are about a dozen places in the code where OCaml creates error messages.  They're spread out amongst all of the tools.

I believe I found them all, but each one requires careful work to avoid breaking things.   So far, I've only changed the one in ocamlc.  After finding them, I'll also need to learn how to trigger each of them to even test the change.

That's why I don't want to do it unless it's really useful to people.  

I don't use emacs right now so I don't know how to test that part of the system.  Will using the standard Gnu error format be ok with what Daniel Bünzli was concerned about? 

Bill

--------------080809000804000808080907--