Re: [HACKERS] Re: [PORTS] Port Bug Report: int2 negative numbers not parsed correctly

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: hackers(at)postgresql(dot)org, mdalphin(at)sanger(dot)otago(dot)ac(dot)nz
Subject: Re: [HACKERS] Re: [PORTS] Port Bug Report: int2 negative numbers not parsed correctly
Date: 1998-04-01 16:23:21
Message-ID: 352269F9.9C57968B@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > Well we maybe can, but it sure is ugly. This will be spread around a
> > bunch of places (everywhere there is a unary minus allowed). I
> > already did the wrong thing and brute-forced something similar into
> > the CREATE SEQUENCE code in gram.y. Isolating it in transform_expr()
> > or somewhere like that would be much cleaner.
> But isn't it is just one line in gram.y. That is where I was seeing
> it happen.

golem$ grep UMINUS gram.y
%right UMINUS
| '-' default_expr %prec UMINUS
| '-' constraint_expr %prec UMINUS
| '-' a_expr %prec UMINUS
| '-' b_expr %prec UMINUS
| '-' position_expr %prec UMINUS

So at least 5 different places, perhaps more when you get into it :(

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sajiah Chmaitelli 1998-04-01 16:28:58 ILLUSTRA DBA CONSULTANT NEEDED ASAP!
Previous Message Bruce Momjian 1998-04-01 16:10:26 Re: [HACKERS] Memory leak while creating indices?