[Issue 8 drafts 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

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

[Issue 8 drafts 0001551]: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters)

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

[1003.1(2016/18)/Issue7+TC2 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

The following issue has been set as RELATED TO issue 0001551. == https://austingroupbugs.net/view.php?id=1550 == Reported By:calestyo

[1003.1(2016/18)/Issue7+TC2 0001551]: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters)

The following issue has been set as RELATED TO issue 0001550. == https://austingroupbugs.net/view.php?id=1551 == Reported By:calestyo

Re: Fwd: sed and delimiters that are also special characters to REs

On Thu, Jan 13, 2022 at 6:36 PM Christoph Anton Mitterer wrote: > And where does it say that? I mean in the standard. > I.e. where does it say, that parsing is only allowed to happen in one > stage from left to right, especially not only with respect to an RE > itself, but also when an RE is

[1003.1(2016/18)/Issue7+TC2 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

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

[1003.1(2016/18)/Issue7+TC2 0001551]: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters)

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

[1003.1(2016/18)/Issue7+TC2 0001550]: clarifications/ambiguities in the description of context addresses and their delimiters for sed

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

Re: sed and delimiters that are also special characters to REs

btw: Things seem even worse, as also non-special characters used as delimiters may be affected by implementation-ambiguities: GNU sed: $ printf '%s\n' '9+' | sed 's+9\++X+' X $ printf '%s\n' '99+' | sed 's+9\++X+' 9X $ printf '%s\n' '999+' | sed 's+9\++X+' 99X => these results are IMO

UTF-8 - an experimental result

(This note is strictly informational: no response needed, but I thought folks might find it interesting or even useful. I'm sending this because the issue of a UTF-8 standard locale was being discussed.) Background: Around 20 years ago, I tried an experiment w.r.t. character set width (8 vs. 16

[Issue 8 drafts 0001526]: Update fdopen() mode description to match new fopen() terminology

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

[Issue 8 drafts 0001526]: Update fdopen() mode description to match new fopen() terminology

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

[1003.1(2016/18)/Issue7+TC2 0001525]: only the close() of the last fd for a socket should destroy the socket

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

[Issue 8 drafts 0001524]: open() flags used by fopen()

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

[1003.1(2016/18)/Issue7+TC2 0001523]: Wrong layout of getopt "-"

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

[Online Pubs 0001523]: Wrong layout of getopt "-"

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

[Online Pubs 0001549]: Escaped newline in macro expansion in command line.

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

Re: Fwd: sed and delimiters that are also special characters to REs

On Thu, 2022-01-13 at 10:04 +0300, Oğuz via austin-group-l at The Open Group wrote: > > a) Is it defined, how the unescaping of delimiters vs. special > > characters happens? > > Consider the following example: > > s(\\((X( > > There are at least two ways to parse that: > > I see only one. From

Re: Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

Yes thank you, this is very helpful. Right now, I point the customers to the current published POSIX standard, when it comes to behaviour that is covered there. However, if they do raise an issue like this, that is already addressed in the draft, I would want to copy-and-paste a section from the

Re: Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

Mark Galeck wrote, on 13 Jan 2022: > > Thank you Nick. So here's the one I just found. > > In the section 2.2.3 Double-Quotes, it says about \ : > > "The shall retain its special meaning as an escape > character (see Escape Character (Backslash)) only when followed by one > of the following

Re: Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

Thank you Nick. So here's the one I just found. In the section 2.2.3 Double-Quotes, it says about \ : "The shall retain its special meaning as an escape character (see Escape Character (Backslash)) only when followed by one of the following characters when considered special: $ ` " \

[Issue 8 drafts 0001520]: make should support the $^ internal macro

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1520 == Reported By:joerg Assigned

[Issue 8 drafts 0001513]: Changes for make missed when :::= was added

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1513 == Reported By:geoffclare

[Issue 8 drafts 0001503]: Potential new M_ constants for math.h

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1503 == Reported By:andras_farkas

[1003.1(2013)/Issue7+TC1 0001496]: Add asprintf() and vasprintf()

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1496 == Reported By:alanc Assigned

[1003.1(2016/18)/Issue7+TC2 0001440]: Calling `system("-some-tool")` fails (although it is a valid `sh` command)

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1440 == Reported By:ciprian_craciun