Re: Non-decimal integer literals
От | John Naylor |
---|---|
Тема | Re: Non-decimal integer literals |
Дата | |
Msg-id | CAFBsxsGcgqJ_KO-1=jCUJKK2z5rCh2qsf7=VgNWzTvakLMDyBQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Non-decimal integer literals (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: Non-decimal integer literals
|
Список | pgsql-hackers |
On Wed, Jan 26, 2022 at 10:10 PM Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote: > [v8 patch] 0001-0004 seem pretty straightforward. 0005: {realfail1} { - /* - * throw back the [Ee], and figure out whether what - * remains is an {integer} or {decimal}. - */ - yyless(yyleng - 1); SET_YYLLOC(); - return process_integer_literal(yytext, yylval); + yyerror("trailing junk after numeric literal"); } realfail1 has been subsumed by integer_junk and decimal_junk, so that pattern can be removed. <SQL>{ +/* + * Note that some trailing junk is valid in C (such as 100LL), so we contain + * this to SQL mode. + */ It seems Flex doesn't like C comments after the "%%", so this stanza was indented in 0006. If these are to be committed separately, that fix should happen here. 0006: Minor nit -- the s/decimal/numeric/ change doesn't seem to have any notational advantage, but it's not worse, either. 0007: I've attached an addendum to restore the no-backtrack property. Will the underscore syntax need treatment in the input routines as well? -- John Naylor EDB: http://www.enterprisedb.com
Вложения
В списке pgsql-hackers по дате отправления: