| From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Token separation |
| Date: | 2012-01-20 13:29:59 |
| Message-ID: | jfbq8n$l8b$1@reversiblemaps.ath.cx |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On 2012-01-16, Tim Landscheidt <tim(at)tim-landscheidt(dot)de> wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>>> [ "0x13" is lexed as "0" then "x13" ]
>
>>> Is this behaviour really conforming to the standard?
>
>> Well, it's pretty much the universal behavior of flex-based lexers,
>> anyway. A token ends when the next character can no longer sensibly
>> be added to it.
>
> I know, but - off the top of my head - in most other lan-
> guages "0abc" will then give a syntax error.
In most other languages "0 abc" would also be a syntax error.
0and doesn't give a syntax error in php
eg: <? echo 0and 0; ?>
--
⚂⚃ 100% natural
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rehan Saleem | 2012-01-22 13:09:55 | How to Return Table From Function |
| Previous Message | Adrian Klaver | 2012-01-19 19:42:12 | Re: date range to set of dates expansion |