From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Vincent Lefevre Newsgroups: gmane.emacs.bugs Subject: bug#50640: 28.0.50; incorrect highlighting in C++ mode Date: Fri, 26 Aug 2022 14:24:08 +0200 Message-ID: <20220826122408.GH61030@zira.vinc17.org> References: <87czp79x6s.fsf@vinc17.net> <87k06vcjtr.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14394"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.7+32 (d84696f2) vl-149028 (2022-08-22) Cc: 50640@debbugs.gnu.org, Alan Mackenzie , Stefan Kangas To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 26 14:33:20 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oRYWW-0003aI-Cv for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 26 Aug 2022 14:33:20 +0200 Original-Received: from localhost ([::1]:38664 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oRYWV-0006sJ-CR for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 26 Aug 2022 08:33:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41070) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oRYOU-0006uX-JB for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 08:25:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34590) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oRYOU-00017c-8s for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 08:25:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oRYOT-0003N9-Pd for bug-gnu-emacs@gnu.org; Fri, 26 Aug 2022 08:25:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Vincent Lefevre Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Aug 2022 12:25:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50640 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 50640-submit@debbugs.gnu.org id=B50640.166151665812904 (code B ref 50640); Fri, 26 Aug 2022 12:25:01 +0000 Original-Received: (at 50640) by debbugs.gnu.org; 26 Aug 2022 12:24:18 +0000 Original-Received: from localhost ([127.0.0.1]:52572 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRYNm-0003M4-2U for submit@debbugs.gnu.org; Fri, 26 Aug 2022 08:24:18 -0400 Original-Received: from joooj.vinc17.net ([155.133.131.76]:39396) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oRYNd-0003Lo-Fk for 50640@debbugs.gnu.org; Fri, 26 Aug 2022 08:24:17 -0400 Original-Received: from smtp-zira.vinc17.net (128.119.75.86.rev.sfr.net [86.75.119.128]) by joooj.vinc17.net (Postfix) with ESMTPSA id 49C78274; Fri, 26 Aug 2022 14:24:08 +0200 (CEST) Original-Received: by zira.vinc17.org (Postfix, from userid 1000) id 24B8828001DF; Fri, 26 Aug 2022 14:24:08 +0200 (CEST) Content-Disposition: inline In-Reply-To: <87k06vcjtr.fsf@gnus.org> X-Mailer-Info: https://www.vinc17.net/mutt/ X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:240827 Archived-At: On 2022-08-26 13:42:24 +0200, Lars Ingebrigtsen wrote: > Alan Mackenzie writes: > > > There's really not much which can be done about this in CC Mode, sorry. > > CC Mode's analysis of ambiguous C++ constructs is not very deep, so it > > sometimes gets it wrong, as here. > > > > I would be in favour of closing this bug as "won't fix" (actually, can't > > fix). > > OK; closing this as a "wontfix", then. Isn't it really possible to have an option to forbid && and || in <...> constructs? I think that this would be useful in practice, because when && or || is involved, < and > around them probably mean comparisons. Note that the issue is more general than nested < .. < .. > .. >. Bad highlighting also occurs just with "a < b || c > d". -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)