Re: [rfc] unicode escapes for extended strings - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: [rfc] unicode escapes for extended strings
Date
Msg-id e51f66da0909090826m3cc51825icb1615cbb9f3b37d@mail.gmail.com
Whole thread Raw
In response to [rfc] unicode escapes for extended strings  (Marko Kreen <markokr@gmail.com>)
Responses Re: [rfc] unicode escapes for extended strings
Re: [rfc] unicode escapes for extended strings
List pgsql-hackers
Unicode escapes for extended strings.

On 4/16/09, Marko Kreen <markokr@gmail.com> wrote:
> Reasons:
>
>  - More people are familiar with \u escaping, as it's standard
>   in Java/C#/Python, probably more..
>  - U& strings will not work when stdstr=off.
>
>  Syntax:
>
>   \uXXXX      - 16-bit value
>   \UXXXXXXXX  - 32-bit value
>
>  Additionally, both \u and \U can be used to specify UTF-16 surrogate
>  pairs to encode characters with value > 0xFFFF.  This is exact behaviour
>  used by Java/C#/Python.  (except that Java does not have \U)

v3 of the patch:

    - convert to new reentrant lexer API
    - add lexer targets to avoid fallback to default
    - completely disallow \U\u without proper number of hex values
    - fix logic bug in surrogate pair handling

--
marko

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: More robust pg_hba.conf parsing/error logging
Next
From: decibel
Date:
Subject: Re: Elementary dependency look-up