14 Ocak 2022 Cuma tarihinde Christoph Anton Mitterer
yazdı:
> Which is impossible again, especially in a portable manner, when it's
> ambiguous what a valid RE is.
Except it's not. Use a delimiter that doesn't appear in the RE and you're
good.
> But since it is neither specified how the parsi
The following issue has been SUBMITTED.
==
https://www.austingroupbugs.net/view.php?id=1552
==
Reported By:calestyo
Assigned To:
A NOTE has been added to this issue.
==
https://www.austingroupbugs.net/view.php?id=1551
==
Reported By:calestyo
Assigned To:
A NOTE has been added to this issue.
==
https://www.austingroupbugs.net/view.php?id=1551
==
Reported By:calestyo
Assigned To:
A NOTE has been added to this issue.
==
https://www.austingroupbugs.net/view.php?id=1551
==
Reported By:calestyo
Assigned To:
A NOTE has been added to this issue.
==
https://www.austingroupbugs.net/view.php?id=1551
==
Reported By:calestyo
Assigned To:
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1549
==
Reported By:dmitry_goncharov
Assigned To:
All
Enclosed are the minutes from yesterday's meeting
regards
Andrew
-
Minutes of the 13th January 2022 TeleconferenceAustin-1190 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 14th December 2021
Attendees:
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1523
==
Reported By:rillig
Assigned To:
=
On Fri, 2022-01-14 at 13:03 +0300, Oğuz wrote:
> Yes you can, and it can be that simple. Providing a valid RE is
> application developer's responsibility
Which is impossible again, especially in a portable manner, when it's
ambiguous what a valid RE is.
> Backslash not being special inside a
> b
OK I understand, that's what I was worried about, some kind of issue like that.
I don't expect any such thing come up from a customer really, it's
unlikely. If it does and the fix is not yet officially published, well
I will handle it without pasting or referring to the draft.
Sorry and thank you
On Fri, 2022-01-14 at 00:10 -0800, Don Cragun wrote:
> It isn't that simple.
IMO it's even more complex ;-)
> When you find the first delimiter, you can't look for the second
> delimiter in the middle of a bracket expression and you can't look
> for the second delimiter in the middle of a subexpr
On Fri, 2022-01-14 at 09:07 +0300, Oğuz 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 embedded in
A NOTE has been added to this issue.
==
https://www.austingroupbugs.net/view.php?id=1551
==
Reported By:calestyo
Assigned To:
Hello Mark
Thanks for your mail. There are various restrictions on the unapproved drafts
imposed
on us by the standards process and the copyright holders, including various
disclaimers and notices of limitations we have to place in the drafts.
In short the drafts are only intended to be used f
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1//
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20120311T02
RRULE:FREQ=YE
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1//
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20120311T02
RRULE:FREQ=YE
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1549
==
Reported By:dmitry_goncharov
Assigned To:
On Fri, Jan 14, 2022 at 11:10 AM Don Cragun wrote:
> It isn't that simple. The string between the first and second delimiters in
> a substitute command has to be an RE (and "[" can't be the end of an RE; it
> is the start of a bracket expression). Note also that is not
> special inside a bra
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=1549
==
Reported By:dmitry_goncharov
Assigned To:
The following issue has been UPDATED.
==
https://austingroupbugs.net/view.php?id=1549
==
Reported By:dmitry_goncharov
Assigned To:
> On Jan 13, 2022, at 10:07 PM, Oğuz via austin-group-l at The Open Group
> wrote:
>
> 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 fr
22 matches
Mail list logo