Re: [RFC] Desire to move RFC add_str_begin_and_end_functions to a vote

On 22 June 2019 20:56:24 BST, Ben Ramsey <ben@benramsey.com> wrote: >Perhaps it would only be an issue with the case-insensitive versions, >as Nikita points out? If so, can someone provide some example strings >where an mb_starts_with_ci() would return true, while >str_starts_with_ci() would return false? That's easy: any character that has a lower- and uppercase form, and is not represented as one byte in the target encoding. For that matter, any such character in the non-ASCII section of a single-byte encoding, since a non-mbstring case insensitive flag would presumably leave everything other than ASCII letters untouched. So, any non-Latin script, like Greek or Cyrillic; any accented characters, unless you're lucky and they're represented by ASCII-letter plus combining modifier; the Turkish "i", which if I remember rightly has three forms not two; and so on. Regards, -- Rowan Collins [IMSoP]