Groups > muc.lists.netbsd.tech.toolchain > #3628

Re: 10.1 make oddity

Path	csiph.com!weretis.net!feeder8.news.weretis.net!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.karotte.org!news.space.net!news.muc.de!.POSTED.news.muc.de!not-for-mail
From	David Holland <dholland-tech@netbsd.org>
Newsgroups	muc.lists.netbsd.tech.toolchain
Subject	Re: 10.1 make oddity
Date	Wed, 10 Jun 2026 21:03:52 +0000
Organization	Newsgate at muc.de e.V.
Sender	tech-toolchain-owner@NetBSD.org
Approved	news-admin@muc.de
Distribution	world
Message-ID	<ainROMauCLmtEsEX@netbsd.org> (permalink)
References	<5d6cee50-1132-4faf-b364-5b67b47464eb@gmx.de> <>
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Injection-Info	news.muc.de; posting-host="news.muc.de:193.149.48.2"; logging-data="84041"; mail-complaints-to="news-admin@muc.de"
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=netbsd.org; s=20240131; t=1781125434; bh=ukrQQ4WBTEE/PV3f2L7MnCXCdJt69iatp9iXSc8nf9I=; h=Date:From:To:Subject:References:In-Reply-To:List-Id: List-Unsubscribe; b=lPRCraxnR9ACARyxQtUv0Jajbx5JviuZ49MobVOkfVsJShDyfJwQjaKhLunX1AiUD b4c+0ywzPaVpYTuOBTv0LQ6gBTDlAI2Vtzfrj1aIp297LlMWBG9kHatUqA0zZt5lie oZMQ/VEe7mYXdWHGP93GuwR5MQm7M5OUUCHrkdNY=
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=netbsd.org; s=20240131; t=1781125433; bh=ukrQQ4WBTEE/PV3f2L7MnCXCdJt69iatp9iXSc8nf9I=; h=Date:From:To:Subject:References:In-Reply-To; b=XvRqNjNe/luK6P6E7xq5dXgT5t9wqjd5EXorR1l6isJz+keZfqfYTNhjsl+xzbz9N mgo0/qK2KLqiCVVifW/NoGSp0UCGPCMCLMmjVWeauFC69XE58wjRABCXo9zPR4lDak MiQ9Id0BH9lZw4nWg8UZu1urvhQzisHPzMgUfelY=
Content-Disposition	inline
In-Reply-To	<5d6cee50-1132-4faf-b364-5b67b47464eb@gmx.de>
Precedence	bulk
X-Newsgate-Id	f02c70b8849f+
X-No-Archive	Yes
Xref	csiph.com muc.lists.netbsd.tech.toolchain:3628

Show key headers only | View raw

On Tue, Jun 09, 2026 at 12:41:58PM +0200, Roland Illig wrote:
 > I fixed the code for finding the semicolon so that it conforms to your
 > interpretation, assuming that many other people expect the same.
 > Splitting the line in the middle of an expression was so surprising that
 > I had to step through the code to find the accurate explanation.

One of these years we really do need to fix the parser to never rescan
anything, which will eliminate most of this kind of trouble. But I am
not going to get to it anytime soon...

-- 
David A. Holland
dholland@netbsd.org

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

Back to muc.lists.netbsd.tech.toolchain | Previous — Previous in thread | Find similar | Unroll thread

Thread

10.1 make oddity Mouse <mouse@Rodents-Montreal.ORG> - 2026-06-08 19:13 -0400
  Re: 10.1 make oddity Roland Illig <roland.illig@gmx.de> - 2026-06-09 03:06 +0200
    Re: 10.1 make oddity Mouse <mouse@Rodents-Montreal.ORG> - 2026-06-08 22:04 -0400
      Re: 10.1 make oddity Roland Illig <roland.illig@gmx.de> - 2026-06-09 10:31 +0200
    Re: 10.1 make oddity Edgar Fuß <ef@math.uni-bonn.de> - 2026-06-09 11:44 +0200
      Re: 10.1 make oddity Roland Illig <roland.illig@gmx.de> - 2026-06-09 12:41 +0200
        Re: 10.1 make oddity David Holland <dholland-tech@netbsd.org> - 2026-06-10 21:03 +0000

csiph-web