From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Herring, Davis" Newsgroups: gmane.emacs.devel Subject: Re: Thoughts on getting correct line numbers in the byte compiler's warning messages Date: Tue, 6 Nov 2018 04:34:30 +0000 Message-ID: <9501281ffee54511aa682d04a5b01e11@lanl.gov> References: <20181101175953.GC4504@ACM> <20181105105302.GA10520@ACM> <83y3a7cya8.fsf@gnu.org>,<20181105165137.GB10520@ACM> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1541478881 19018 195.159.176.226 (6 Nov 2018 04:34:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 6 Nov 2018 04:34:41 +0000 (UTC) Cc: Eli Zaretskii , "monnier@iro.umontreal.ca" , "emacs-devel@gnu.org" To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 06 05:34:36 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gJt4W-0004qM-Fj for ged-emacs-devel@m.gmane.org; Tue, 06 Nov 2018 05:34:36 +0100 Original-Received: from localhost ([::1]:38887 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJt6c-0007bf-M4 for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2018 23:36:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60357) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJt5a-0007bO-Px for emacs-devel@gnu.org; Mon, 05 Nov 2018 23:35:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJt5X-00054Z-7u for emacs-devel@gnu.org; Mon, 05 Nov 2018 23:35:42 -0500 Original-Received: from proofpoint8.lanl.gov ([204.121.3.47]:57158) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gJt5U-0004m7-VO; Mon, 05 Nov 2018 23:35:39 -0500 Original-Received: from pps.filterd (proofpoint8.lanl.gov [127.0.0.1]) by proofpoint8.lanl.gov (8.16.0.22/8.16.0.22) with SMTP id wA64YVw6145180; Mon, 5 Nov 2018 21:34:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lanl.gov; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=lanl; bh=lyTgktIelhn3mrHwxY50uA3RbqTyhhXo31kyZvy81hI=; b=bqgankaQZOs911gWsn7kfkDggFwJquw9vcYG2GIhrs46EbxYRRVhn+hMwCpX5gWYXjOD pFNzHmRSV6bLbudEDXVBevJLf1YFk7jwej6p6ODWQdZbfAv/FeMPGHDhi8GAqAM3JZ2O kyxPtgyLA/gLNOid27vjDxv3yG1fZmp4KTOFhBIYn2IW7/QPY0yMtn32I9EcE+hcFTWY esGOBVu7+Kz0Ppn3s4cRpGF127a1nnn1SL2azvbgDQJlmlhHQUpjMaam3Tcyqu2KYEA/ LrMTg6/OI0PuUA/gK/V+TbWw1iCXJoOE+/A/Q0Ga6jDwcF6nRarssRg8iRuC5mxUKkuC Dg== Original-Received: from mailrelay1.lanl.gov (mailrelay1.lanl.gov [128.165.4.101]) by proofpoint8.lanl.gov with ESMTP id 2nh8f1uf5j-1; Mon, 05 Nov 2018 21:34:31 -0700 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by mailrelay1.lanl.gov (Postfix) with ESMTP id 2D2ED13F302D; Mon, 5 Nov 2018 21:34:31 -0700 (MST) X-NIE-2-Virus-Scanner: amavisd-new at mailrelay1.lanl.gov Original-Received: from EXG16-P-MBX01.win.lanl.gov (exg16-p-mbx01.win.lanl.gov [128.165.106.181]) by mailrelay1.lanl.gov (Postfix) with ESMTP id 1733713F2760; Mon, 5 Nov 2018 21:34:31 -0700 (MST) Original-Received: from EXG16-P-MBX03.win.lanl.gov (128.165.106.183) by EXG16-P-MBX01.win.lanl.gov (128.165.106.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1531.3; Mon, 5 Nov 2018 21:34:30 -0700 Original-Received: from EXG16-P-MBX03.win.lanl.gov ([fe80::b49f:6289:af47:79b3]) by EXG16-P-MBX03.win.lanl.gov ([fe80::b49f:6289:af47:79b3%2]) with mapi id 15.01.1531.007; Mon, 5 Nov 2018 21:34:30 -0700 Thread-Topic: Thoughts on getting correct line numbers in the byte compiler's warning messages Thread-Index: AQHUcgzWFRgfKhweak+DuOOzj4coT6U7iEVYgAX0bAD//+LnfoAAgUiAgABNvIE= In-Reply-To: <20181105165137.GB10520@ACM> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.165.106.203] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-06_02:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=907 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811060037 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 204.121.3.47 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:231037 Archived-At: > I've spend many hours at my PC, trying to figure out a neat way of > solving this problem. The above is the best I've been able to come up > with, so far. Considering patterns like AoS vs. SoA, could the reader produce (on demand)= a pair: the expression read and a parallel structure of position informati= on? For example, '(foo bar [baz]) =3D> ((quote (foo bar)) . (0 (2 6 [11]))) where the numbers are character offsets from the beginning of the read? Th= is loses information on the opening delimiter for each list/cons/vector; it= could be added with certain obvious alterations to the location structure = if that's a problem. Davis=