On Fri, May 17, 2024 at 9:33 PM Collin Funk via austin-group-l at The
Open Group wrote:
> I am not sure how to make an account on the bug tracker. If it is
> preferred that this is submitted there I am happy to do so. I just
> need help with registration.
>
> I am using the 202x Draft 4.1
(Away from computer with credentials for the bug tracker, so just replying
here)
Format of the output isn’t defined (and differs substantially between at
least FreeBSD and GNU utilities).
Nothing prevents confstr() values from containing new lines, which makes
the output ambiguous.
(The
I just noticed that waitid() is not included in the list of
async-signal-safe interfaces, at least as of TC2. Was that an intentional
decision or an oversight? Is there a known existing implementation where
it isn't?
(...or did I miss an existing bug about this?)
Philip Guenther
On Mon, Nov 1, 2021 at 12:02 PM Wayne Pollock via austin-group-l at The
Open Group wrote:
> On 11/1/2021 9:12 AM, Eric Blake wrote:
> > On Sat, Oct 30, 2021 at 08:21:55PM -0400, Wayne Pollock via
> austin-group-l at The Open Group wrote:
> >> Is it guaranteed that on conforming systems nohup
On Mon, Jun 28, 2021 at 2:53 PM Vincent Lefevre via austin-group-l at The
Open Group wrote:
> On 2021-06-28 21:28:37 +0700, Robert Elz wrote:
> > Date:Mon, 28 Jun 2021 15:48:33 +0200
> > From:Vincent Lefevre
> > Message-ID: <20210628134833.ga46...@zira.vinc17.org>
>
de is
> expected to use the work alike octal escape, not hex codes.
>
> On Fri, Apr 16, 2021 at 12:05 AM, Philip Guenther via austin-group-l at
> The Open Group
> wrote:
> The general question is what requirements the standard put on the printf
> utility when the format argume
Correction after off-list poke: FreeBSD's /usr/bin/printf and the printf
builtin to /bin/sh both show "x61"
On Thu, Apr 15, 2021 at 7:04 PM Philip Guenther wrote:
> The general question is what requirements the standard put on the printf
> utility when the format argument contains a \x or other
The general question is what requirements the standard put on the printf
utility when the format argument contains a \x or other unspecified
backslash escape, but the example in the subject is a nice concrete
example: what's required for or about the output of
printf '\x61'
?
1003.1-2016
I agree with Robert on this. Bumping the value of these macros when
there's no change to the specified behavior of the relevant functionality
provides no benefit and is actively harmful to code being forward portable.
Yes, this makes the text of the specification for these more complex, while
On Wed, Dec 2, 2020 at 11:15 AM Schwarz, Konrad via austin-group-l at The
Open Group wrote:
> after some (moderate) digging, it seems like the interfaces documented in
> net/if.h are not related to anything else defined in POSIX.
>
>
>
> To recap, the routines declared there provide a mapping
On Tue, Sep 1, 2020 at 1:20 PM Steffen Nurpmeso wrote:
> Philip Guenther wrote in
> :
> |On Tue, Sep 1, 2020 at 6:22 AM Steffen Nurpmeso via austin-group-l at The
> |Open Group wrote:
> |> Robert Elz via austin-group-l at The Open Group wrote in
> |> <9252.1598969...@jinx.noi.kre.to>:
>
On Tue, Sep 1, 2020 at 6:22 AM Steffen Nurpmeso via austin-group-l at The
Open Group wrote:
> Robert Elz via austin-group-l at The Open Group wrote in
> <9252.1598969...@jinx.noi.kre.to>:
> |Date:Tue, 1 Sep 2020 10:32:55 +0100
> |From:"Geoff Clare via austin-group-l at
On Tue, Sep 1, 2020 at 5:40 AM Geoff Clare via austin-group-l at The Open
Group wrote:
> > --
> > (0004958) philip-guenther (reporter) - 2020-08-30 23:06
> > https://austingroupbugs.net/view.php?id=6
>
13 matches
Mail list logo
