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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 79CCF7EE51 for ; Sun, 14 Apr 2013 22:02:07 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of madroach@gmerlin.de) identity=pra; client-ip=80.91.229.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="madroach@gmerlin.de"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of gclci-caml-list@m.gmane.org designates 80.91.229.3 as permitted sender) identity=mailfrom; client-ip=80.91.229.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="gclci-caml-list@m.gmane.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@plane.gmane.org designates 80.91.229.3 as permitted sender) identity=helo; client-ip=80.91.229.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="gclci-caml-list@m.gmane.org"; x-sender="postmaster@plane.gmane.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvwAADkKa1FQW+UDmWdsb2JhbABQhmy/FRYOAQEBAQEICwsHFCiCHwEBBAEjDwFLCwsaAiYCAlcZiA4KqBORVoEjjhGCGIETA5cElB8 X-IPAS-Result: AvwAADkKa1FQW+UDmWdsb2JhbABQhmy/FRYOAQEBAQEICwsHFCiCHwEBBAEjDwFLCwsaAiYCAlcZiA4KqBORVoEjjhGCGIETA5cElB8 X-IronPort-AV: E=Sophos;i="4.87,471,1363129200"; d="scan'208";a="13212391" Received: from plane.gmane.org ([80.91.229.3]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES256-SHA; 14 Apr 2013 22:02:06 +0200 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1URT7l-0005d7-Mx for caml-list@inria.fr; Sun, 14 Apr 2013 22:02:05 +0200 Received: from stgt-d9be592e.pool.mediaways.net ([217.190.89.46]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Apr 2013 22:02:05 +0200 Received: from madroach by stgt-d9be592e.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Apr 2013 22:02:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Christopher Zimmermann Date: Sun, 14 Apr 2013 22:01:55 +0200 Message-ID: <20130414220155.94e847e46004cfb5dfca431b@gmerlin.de> References: <516AC928.9030400@emu-bark.com> <93F65479FCAB425282517E571DA027D9@erratique.ch> <516AF334.2040202@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: stgt-d9be592e.pool.mediaways.net X-Newsreader: Sylpheed 3.2.0 (GTK+ 2.24.13; i386-unknown-openbsd5.2) X-Validation-by: madroach@gmerlin.de Subject: [Caml-list] Re: modified error messages for ocamlc On Sun, 14 Apr 2013 20:18:21 +0100 Daniel Bünzli wrote: > Le dimanche, 14 avril 2013 à 19:19, Jonathan Protzenko a écrit : > > The OCaml mode for emacs that's distributed along with the OCaml > > sources contains (caml.el) : > > > > 796 ;; Newer emacs versions support line/char ranges > > 797 ;; We will adapt OCaml to output error messages in a > > compatible format. > > 798 ;; In the meantime we add the new format here in addition to > > the old one. > > 799 (defconst caml-error-regexp-newstyle > > 800 "^[ A-\377]+ \"\\([^\"\n]+\\)\", line \\([0-9]+\\), char > > \\([0-9]+\\) to line \\([0-9]+\\), char \\([0-9]+\\):" > > 801 "Regular expression matching the error messages produced by > > ocamlc/ocamlopt.") > > > > So there are provisions already in the Emacs mode for parsing > > multi-line error formats. What refrains us from switching directly > > to the format that's recognized by the already-distributed Caml > > mode ? > > > This discussion is very confusing. There's nothing special to be done > here, it already works… The "old" version of the original message > does exactly what it needs to do to highlight multiline errors. Yes for emacs, no for everyone else and especially for humans reading the compiler output with their own eyes. Christopher