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 2A4E67EE51 for ; Sun, 14 Apr 2013 17:20:14 +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.234; 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.234; 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@p3plsmtpa07-05.prod.phx3.secureserver.net) identity=helo; client-ip=173.201.192.234; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bills@emu-bark.com"; x-sender="postmaster@p3plsmtpa07-05.prod.phx3.secureserver.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnoCALfGalGtycDqemdsb2JhbABQgzwBiQ25NhYOAQEJDQkJESuCTVEgHRYYAwIBAgE/DA0IAQGIEJlGoCaSXwOYJoRkjjM X-IPAS-Result: AnoCALfGalGtycDqemdsb2JhbABQgzwBiQ25NhYOAQEJDQkJESuCTVEgHRYYAwIBAgE/DA0IAQGIEJlGoCaSXwOYJoRkjjM X-IronPort-AV: E=Sophos;i="4.87,471,1363129200"; d="scan'208,217";a="10906976" Received: from p3plsmtpa07-05.prod.phx3.secureserver.net ([173.201.192.234]) by mail3-smtp-sop.national.inria.fr with ESMTP; 14 Apr 2013 17:20:11 +0200 Received: from [192.168.0.2] ([173.26.186.224]) by p3plsmtpa07-05.prod.phx3.secureserver.net with id PrL71l0074qv3b901rL7KE; Sun, 14 Apr 2013 08:20:08 -0700 Message-ID: <516AC928.9030400@emu-bark.com> Date: Sun, 14 Apr 2013 11:20:08 -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="------------040503050700020309060400" Subject: [Caml-list] modified error messages for ocamlc This is a multi-part message in MIME format. --------------040503050700020309060400 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I've made a change to my copy of ocamlc to modify error messages when they cover multiple lines. For example, for the following code, the modified error message includes the line number and character offset of then end of the message instead of just the length of the message. Would there be any interest in me making the change everywhere and submitting it as a patch? I see about a dozen places in the source of the various tools where the change would be possible. One concern I have is that it might break automated test scripts. Bill Smith let x = 1 in (match x with 1 -> true );; -------- New: File "multilineError.ml", line 2, character 0-line 4, character 1: Warning 8: this pattern-matching is not exhaustive. Here is an example of a value that is not matched: 0 -------- Old: File "multilineError.ml", line 2, characters 0-28: Warning 8: this pattern-matching is not exhaustive. Here is an example of a value that is not matched: 0 --------------040503050700020309060400 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi,

I've made a change to my copy of ocamlc to modify error messages when they cover multiple lines.

For example, for the following code, the modified error message includes the line number and character offset of then end of the message instead of just the length of the message.

Would there be any interest in me making the change everywhere and submitting it as a patch? I see about a dozen places in the source of the various tools where the change would be possible. One concern I have is that it might break automated test scripts.

Bill Smith

let x = 1 in
(match x with
1 -> true
);;
--------
New:
File "multilineError.ml", line 2, character 0-line 4, character 1:
Warning 8: this pattern-matching is not exhaustive.
Here is an example of a value that is not matched:
0
--------
Old:
File "multilineError.ml", line 2, characters 0-28:
Warning 8: this pattern-matching is not exhaustive.
Here is an example of a value that is not matched:
0

--------------040503050700020309060400--