[1003.1(2016/18)/Issue7+TC2 0001436]: make: add "-j max_jobs" option to support simultaneous rule processing

The following issue has been set as RELATED TO issue 0001660. == https://austingroupbugs.net/view.php?id=1436 == Reported By:steffen

[Issue 8 drafts 0001660]: Out of date make rationale about -n and $(MAKE)

The following issue has been set as RELATED TO issue 0001436. == https://austingroupbugs.net/view.php?id=1660 == Reported By:geoffclare

[Issue 8 drafts 0001661]: Description of .WAIT needs "if any" additions

The following issue has been set as RELATED TO issue 0001437. == https://austingroupbugs.net/view.php?id=1661 == Reported By:geoffclare

[Issue 8 drafts 0001661]: Description of .WAIT needs "if any" additions

The following issue has been SUBMITTED. == https://austingroupbugs.net/view.php?id=1661 == Reported By:geoffclare Assigned To:

[Issue 8 drafts 0001660]: Out of date make rationale about -n and $(MAKE)

The following issue has been SUBMITTED. == https://austingroupbugs.net/view.php?id=1660 == Reported By:geoffclare Assigned To:

Re: $? behaviour after comsub in same command

5 Nisan 2023 Çarşamba tarihinde Harald van Dijk yazdı: > There is a legitimate benefit to this: swapping variables without an > additional helper variable actually works in that implementation. Good point, thanks -- Oğuz

[1003.1(2016/18)/Issue7+TC2 0001437]: make: (document .NOTPARALLEL and .WAIT special targets) in RATIONALE

The following issue has been set as RELATED TO issue 0001661. == https://austingroupbugs.net/view.php?id=1437 == Reported By:steffen

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

Re: $? behaviour after comsub in same command

On 4/5/23 12:36 PM, Harald van Dijk wrote: On 05/04/2023 15:35, Chet Ramey via austin-group-l at The Open Group wrote: On 4/5/23 9:06 AM, Martijn Dekker via austin-group-l at The Open Group wrote: Consider: false || echo $(true) $? dash, mksh and yash print 1. bash, ksh93 and zsh print

[1003.1(2016/18)/Issue7+TC2 0001648]: Confusing description of ASYNCHRONOUS EVENTS default behaviour

The following issue has been RESOLVED. == https://www.austingroupbugs.net/view.php?id=1648 == Reported By:geoffclare Assigned To:

[1003.1(2008)/Issue 7 0000700]: Clarify strtoul's behaviour on strings representing negative numbers

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=700 == Reported By:fbauzac Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001648]: Confusing description of ASYNCHRONOUS EVENTS default behaviour

The following issue has been UPDATED. == https://www.austingroupbugs.net/view.php?id=1648 == Reported By:geoffclare Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

The following issue NEEDS AN INTERPRETATION. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

[1003.1(2008)/Issue 7 0000700]: Clarify strtoul's behaviour on strings representing negative numbers

The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=700 == Reported By:fbauzac Assigned To:

Re: $? behaviour after comsub in same command

On 4/6/23 1:55 PM, Harald van Dijk wrote: One additional data point: in schily-2021-09-18, Jörg's last release, obosh, the legacy non-POSIX shell that is just there for existing scripts and for portability testing, prints 0 (using `` rather than $()), whereas pbosh and sh, the minimal and

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

Re: [PATCH] sockaddr.3type: Document that sockaddr_storage is the API to be used

On Thu, Apr 06, 2023 at 02:05:15PM -0400, Zack Weinberg wrote: > On Thu, Apr 6, 2023, at 12:31 PM, Alejandro Colomar via Libc-alpha wrote: > > On 4/6/23 18:24, Eric Blake wrote: > >> here's the updated wording that the Austin Group tried today (and we > >> plan on starting a 30-day interpretation

Re: $? behaviour after comsub in same command

Date:Wed, 5 Apr 2023 10:35:58 -0400 From:"Chet Ramey via austin-group-l at The Open Group" Message-ID: | A variant with slightly different semantics: | | (exit 8) | a=4 b=$(exit 42) c=$? | echo status:$? c=$c | | The standard is clear about what $?

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

Re: $? behaviour after comsub in same command

Date:Thu, 6 Apr 2023 11:17:43 -0400 From:"Chet Ramey via austin-group-l at The Open Group" Message-ID: <023c0028-e682-e1b6-99db-c8a596cdf...@case.edu> | My question is why they would choose something other than | what the so-called reference implementations

Re: $? behaviour after comsub in same command

On 06/04/2023 16:17, Chet Ramey wrote: On 4/5/23 12:36 PM, Harald van Dijk wrote: On 05/04/2023 15:35, Chet Ramey via austin-group-l at The Open Group wrote: On 4/5/23 9:06 AM, Martijn Dekker via austin-group-l at The Open Group wrote: Consider: false || echo $(true) $? dash, mksh and

Re: $? behaviour after comsub in same command

On 06/04/2023 20:03, Chet Ramey via austin-group-l at The Open Group wrote: On 4/6/23 1:55 PM, Harald van Dijk wrote: One additional data point: in schily-2021-09-18, Jörg's last release, obosh, the legacy non-POSIX shell that is just there for existing scripts and for portability testing,

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

Re: $? behaviour after comsub in same command

On 05/04/2023 18:05, Harald van Dijk via austin-group-l at The Open Group wrote: On 05/04/2023 17:44, Oğuz wrote: 5 Nisan 2023 Çarşamba tarihinde Harald van Dijk > yazdı:     I am not sure which other ash based shells you were looking at, /bin/sh on NetBSD and FreeBSD

Re: $? behaviour after comsub in same command

Date:Fri, 7 Apr 2023 05:38:16 +0300 From:=?UTF-8?B?T8SfdXo=?= Message-ID: | a=${b#prefix} a=${a%suffix} | | is common enough a pattern to consider despite having no benefit other than | looking organized. Most shells interpret it the way average user

[1003.1(2016/18)/Issue7+TC2 0001641]: sockaddr_storage is not alias safe

The following issue has been UPDATED. == https://austingroupbugs.net/view.php?id=1641 == Reported By:bastien Assigned To:

Re: $? behaviour after comsub in same command

7 Nisan 2023 Cuma tarihinde Robert Elz via austin-group-l at The Open Group yazdı: > My guess (no more than that) is that sometimes it is easier to > give in to the desires of the masses rather than maintain the > correct approach. > > To people who don't understand sh syntax, > > a=1

Minutes of the 6th April 2023 Teleconference

All Enclosed are the minutes from the Thursday call this week. Note the next scheduled call is next Thursday regards Andrew --- Minutes of the 6th April 2023 TeleconferenceAustin-1305 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 7th April 2023 Attendees:

Re: $? behaviour after comsub in same command

Robert Elz wrote in <6906.1680741...@jacaranda.noi.kre.to>: ... |The issue here is that people tend to think of | a=1 |as a command. It isn't (not as people think of it anyway). |But with that mindset they treat | a=1 b=$a c=$b |as 3 commands, one after the other. It isn't. To come

Re: $? behaviour after comsub in same command

Date:Fri, 07 Apr 2023 03:14:47 +0200 From:Steffen Nurpmeso Message-ID: <20230407011447.ptyvc%stef...@sdaoden.eu> | There i say I'll omit the quotes from the standard... | So everything should be handled sequentially, making it a bug. >From where do you get