From owner-sc22wg14+sc22wg14-domo2=www.open-std.org@open-std.org Tue Aug 26 02:46:39 2025 Return-Path: X-Original-To: sc22wg14-domo2 Delivered-To: sc22wg14-domo2@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 67022356BDB; Tue, 26 Aug 2025 02:46:39 +0200 (CEST) Delivered-To: sc22wg14@open-std.org Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) by www.open-std.org (Postfix) with ESMTP id 05A55356689 for ; Tue, 26 Aug 2025 02:46:38 +0200 (CEST) Received: by mail-lf1-f42.google.com with SMTP id 2adb3069b0e04-55f4926e0b0so1247639e87.3 for ; Mon, 25 Aug 2025 17:46:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1756169198; x=1756773998; darn=open-std.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MUGQ31lpYiwMEO6NiX9gzzRhVsYePDTbJTPL/8fPh7k=; b=jInn3o5Z0h1apqJR0b2tJ0ylHnFFvTBe+PHSy6DNSlF1gHmd+2wfz1x0Yu79+4DkZ+ 2/CBG8cNnkmtYYX7pGQbjhwkL8Erx6DO5ctjVK4t+FqYE3IWW8bARiOgWJcubeelWNdj Gky0JrbZyYECilmRfZsdMMkkGl7NU2fewyh86ZVqF1m8w3HCcgqLpHLQHzSRlx8gmOiO WID61SSnj4H7dm4+4ruI1m6rRaNkfKj0UkJRL9uAIRzh4C1DKjznCk9GKvjyuHFBhcJ5 0tPoWK1hJMbsssp3LEGE7/bVE0783SdHiM2TJcMsWP/j3s745GRk1habictb3dD123KV +Ing== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756169198; x=1756773998; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MUGQ31lpYiwMEO6NiX9gzzRhVsYePDTbJTPL/8fPh7k=; b=V8ZYT2SCJtuprCIEnnG+9TcDRhXgBKmVtBd8EswmGzYfXPadxg/j2QcJ4Dc7jd9oWo vvqd4Y3IRbrzzEfj3zWo1HOQ526L46qV12up9qZoxO3cExsGW1+2Q2CcCO2UAay41GX/ 3TV4hk8ZxK0PI+2U8HwQxqyYXPukout05YFAA83RH+GQUBcYQ9VzKQHccq0zV0U5jjNQ p8pUSGVyedaOnwzuzTuxaU7yhNxn/KE21TLONxTpO5x3gFYWwGbt2aTmt2siJ/n0K+dd ysHbPRIKCvIBoqSLbRdSuw5Zp9CgbREqKjh7nFhdPAc+wYnqq7DeYK9RTaTPZj+9H3VF PvFg== X-Gm-Message-State: AOJu0Yy+ASOukMGtDyXbx+GnwuMderfyR4820ejBOqYiCxzxVcTNafan MAszDWIYklXGnAAogr4HayUz0mW7mzUnpCc02VBV64vakSGbAyvng+I0EtOunpxlExoP49sgUio AddWLNcVAwx40l2UjnYb6IENJPeLSu1bOUEPN X-Gm-Gg: ASbGnctnU2aX8l8Cm4ToUhKDsrz+NlWXE9pmXPUhbEo8CTGbCDSWTKjDNxsWLWkkL+g DikCIwpV/NmKYBq8CnOs3UMndR3ZvYhyowplCnsuSz6jedeRZRjTJC6biU8dO1gRRM04JNseGTT 83w23MqOSkQhDMlRz/oQ5UAFjtOtuDveFKJNk2Pkwpmzelb+yy9Aena+Zy37sEyTAi/644opI+B E+OtTATUi9C4SHFaQuaEiQ= X-Google-Smtp-Source: AGHT+IF8rLbr+GZFvIJtQlfqq+3mYWx0d7alLiQVFlqxD/SfwefDdEfGkgIVPXbdfXjao3R1I6f0O1neh0DmzLYdfUg= X-Received: by 2002:a05:6512:1516:20b0:55f:33e0:9602 with SMTP id 2adb3069b0e04-55f33e09666mr2642618e87.9.1756169197957; Mon, 25 Aug 2025 17:46:37 -0700 (PDT) MIME-Version: 1.0 References: <20250307181829.636C7356854@www.open-std.org> <20250825190136.8E691356B93@www.open-std.org> In-Reply-To: <20250825190136.8E691356B93@www.open-std.org> From: Robert Seacord Date: Tue, 26 Aug 2025 02:46:24 +0200 X-Gm-Features: Ac12FXwIjyA-7E1BBFZEKX-umq-6kX80Dm5cPg_a3bQ5O-v2wHD9RVeDrLLcuFI Message-ID: Subject: Re: [SC22WG14.33426] New issue #1004: Classification of `scanf` failures To: Joseph Myers Cc: sc22wg14@open-std.org Content-Type: multipart/alternative; boundary="00000000000035b331063d3a01db" Sender: owner-sc22wg14@open-std.org Precedence: bulk --00000000000035b331063d3a01db Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I would prefer the following, simpler language: Failures are classified as input failures due to the occurrence of an encoding error or the unavailability of input characters), or as matching failures due to inappropriate input or an unsupported specific width length modifier. Thanks, rCs On Mon, Aug 25, 2025 at 9:01=E2=80=AFPM Joseph Myers = wrote: > Given the desire in the meeting today to make this a matching failure > rather than a third kind of failure, I propose the following wording > (subclause references based on C23). > > In 7.23.6.3 (The fscanf function), after "Failures are described as input > failures (due to the occurrence of an encoding error or the unavailabilit= y > of input characters), or matching failures (due to inappropriate input)." > insert "If the implementation does not support a specific width length > modifier, this is a matching failure.". Remove "or if the implementation > does not support a specific width length modifier" under Returns. > > Make the same changes in 7.31.2.3 (The fwscanf function). > > This would also supersede all the changes for scanf functions for issue > #1012. > > -- > Joseph S. Myers > josmyers@redhat.com > > --00000000000035b331063d3a01db Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I would prefer the following, simpler=C2=A0language:= =C2=A0

Failures are=C2=A0classified as input= failures due to the occurrence of an encoding error or the unavailability = of input
characters), or as matching failures due to inappropriate input= or an unsupported specific width length modifier.

Thanks,
rCs

On Mon, Aug 25, 2025 at 9= :01=E2=80=AFPM Joseph Myers <josm= yers@redhat.com> wrote:
Given the desire in the meeting today to make this a matchin= g failure
rather than a third kind of failure, I propose the following wording
(subclause references based on C23).

In 7.23.6.3 (The fscanf function), after "Failures are described as in= put
failures (due to the occurrence of an encoding error or the unavailability =
of input characters), or matching failures (due to inappropriate input).&qu= ot;
insert "If the implementation does not support a specific width length=
modifier, this is a matching failure.".=C2=A0 Remove "or if the i= mplementation
does not support a specific width length modifier" under Returns.

Make the same changes in 7.31.2.3 (The fwscanf function).

This would also supersede all the changes for scanf functions for issue #1012.

--
Joseph S. Myers
josmyers@redhat.co= m

--00000000000035b331063d3a01db--