Re: Reminder: Review for Zach's parsing library starts on Feb 19th

From: Tom Honermann (tom_at_[hidden])
Date: 2024-02-29 18:08:06

On 2/28/24 11:37 PM, Zach Laine via Boost wrote:
> On Wed, Feb 28, 2024 at 9:18 PM Alan de Freitas via Boost
> <boost_at_[hidden]>  wrote:
>> Boost.Parser Review
> [snip]
>
>>> Does the API match with current best practices?
>> Using the same conventions as Spirit to combine parsers seems like a good
>> design here.
>>
>> I was a little confused about the convention to assume unicode for anything
>> other than char.
>> I'm not sure that's the convention that minimizes surprise.
> The rationale is this: All the other character types in C++ -- every
> one -- advertises that it is a certain Unicode encoding
> (char{8,16,32}_t) or is specifically designed to hold Unicode code
> points (wchar_t).  char is the only exception to this.

Now, Zach, as a long time SG16 participant and contributor, you know 
full well that wchar_t doesn't imply Unicode :)

(On AIX, wchar_t is associated with IBM-eucTW for the zh_TW locale 
<https://www.ibm.com/docs/vi/aix/7.3?topic=representation-wide-character-data>. 
on z/OS, wchar_t is associated with SBCS EBCDIC, DBCS EBCDIC, Unicode, 
or a locale dependent encoding 
<https://www.ibm.com/docs/en/zos/3.1.0?topic=options-convlit-noconvlit>)

Tom.