[Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

2022-04-11 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1564 == Reported By:calestyo Assigned To:

Re: How do I get the buffered bytes in a FILE *?

2022-04-11 Thread Rob Landley via austin-group-l at The Open Group
On 4/11/22 15:41, Rich Felker wrote: >> But I can't find a portable way to do this? > > To give some context to this question, the __freadahead function > present in musl libc was created in 2012 to resolve a conflict between > gnulib, which has traditionally used an #ifdef jungle to provide >

Re: How do I get the buffered bytes in a FILE *?

2022-04-11 Thread Rob Landley via austin-group-l at The Open Group
On 4/11/22 14:20, Another Person Who Did Not CC The List wrote: > On Mon, Apr 11, 2022 at 01:48:06PM -0500, Rob Landley via austin-group-l at > The Open Group wrote: >> A bunch of protocols (git, http, mbox, etc) start with lines of data >> followed by >> a block of data, so it's natural to want

Re: How do I get the buffered bytes in a FILE *?

2022-04-11 Thread Rob Landley via austin-group-l at The Open Group
On 4/11/22 13:54, Person Who Did Not CC The List wrote: > On 4/11/22 2:48 PM, Rob Landley via austin-group-l at The Open Group wrote: > >> But I can't find a portable way to do this? > > There isn't one. How do I request one? (Does WSG14 have a mailing list?) Rob

How do I get the buffered bytes in a FILE *?

2022-04-11 Thread Rob Landley via austin-group-l at The Open Group
A bunch of protocols (git, http, mbox, etc) start with lines of data followed by a block of data, so it's natural to want to call getline() and then handle the data block. But getline() takes a FILE * and things like zlib and sendfile() take an integer file descriptor. Posix lets me get the file

Re: Bug 1550 (was: [1003.1(2016/18)/Issue7+TC2 0001546]: ...)

2022-04-11 Thread Christoph Anton Mitterer via austin-group-l at The Open Group
On Fri, 2022-04-08 at 10:29 +0100, Geoff Clare via austin-group-l at The Open Group wrote: > As you have probably seen, I have posted an updated proposal to > bug 1550. Hopefully that will help with your review. Yes,.. but still haven't gotten around to look into it (and all the others that I

[Issue 8 drafts 0001564]: clariy on what (character/byte) strings pattern matching notation should work

2022-04-11 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1564 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001561]: clarify what kind of data shell variables need to be able to hold

2022-04-11 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1561 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001560]: clarify wording of command substitution

2022-04-11 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1560 == Reported By:calestyo Assigned To:

[Issue 8 drafts 0001562]: printf utility: clarify what is (byte) string an what is character string

2022-04-11 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1562 == Reported By:calestyo Assigned To: