From: Tim Landscheidt <tim@tim-landscheidt.de>
To: pgsql-sql@postgresql.org
Subject: Re: Token separation
Date: Mon, 16 Jan 2012 15:12:26 +0000
Message-ID: <m3d3ajd6lh.fsf@passepartout.tim-landscheidt.de> (raw)
References: <m3ipkd1jho.fsf@passepartout.tim-landscheidt.de>
<17710.1326647758@sss.pgh.pa.us>
Tom Lane <tgl@sss.pgh.pa.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.
> Possibly the documentation should be tweaked to mention the
> number-followed-by-identifier case.
Especially if you consider such cases:
| tim=# SELECT 1D1; SELECT 1E1; SELECT 1F1;
| d1
| ----
| 1
| (1 Zeile)
| ?column?
| ----------
| 10
| (1 Zeile)
| f1
| ----
| 1
| (1 Zeile)
| tim=#
I don't think it's common to hit this, but the documentation
surely could use a caveat. I will write something up and
submit it to -docs.
Thanks,
Tim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tim@tim-landscheidt.de
Subject: Re: Token separation
In-Reply-To: <m3d3ajd6lh.fsf@passepartout.tim-landscheidt.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox