> Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> > Note that EUC_TW or any multibyte encodings that are allowed for
> > backend side, do not contain such ASCII special characters as "|" and
> > should be safe for the parser and the regexp routines.
>
> But the point is that a pg_wchar is being squeezed down to a char.
> PEEK() produces a pg_wchar, no?
Oh I see.
Actually "c" is used soly to judge if it's '|' or some other stop
(ASCII) characters, so there is no need for changing it to pg_wchar
even if it could be squeezed down to a char. However, someday someone
might use c for other purpose, and it would be a good idea to prepare
for such kind of disaster. Will fix.
--
Tatsuo Ishii
