On Fri, Aug 23, 2024 at 12:27:01PM +0200, Alejandro C via austin-group-l
at The Open Group wrote:
> wmemrchr(), and in general w*(), are functions that deal with wide
> characters --which have a fixed width--, not multi-byte characters --which
> have a variable width--.

> Thus, searching backwards for a wc should be a trivial loop:
> [snip] 

I agree that the rationale is incorrect. However, I still agree that
wmemrchr() should not be added to the standard. Not only would it be
invention, but it would boil down to doing work to improve UTF-32
support (in most implementations). UTF-32 is inefficient with little
compensation (since single code points aren't that meaningful in today's
Unicode).

-- 
Jilles Tjoelker

  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
      • Re:... Alejandro C via austin-group-l at The Open Group
        • ... Jilles Tjoelker via austin-group-l at The Open Group
          • ... Steffen Nurpmeso via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to