Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > This would turn off the make failure when an old bison is called from
> > the makefile?
> 
> Rephrase that as "this would give bison the right to fail of its own
> accord, rather than our prejudging its ability to cope."
> 
> Given bison's on-again-off-again track record in recent releases,
> I don't think it's wise to wire in a non-overridable assumption
> that bison < X is broken and bison >= X is good.  A hint that
> bison < X might be broken is fine --- but let's not pretend that
> configure is smarter than the user.

I just don't like to add bloat/document another configure option that
has a _very_ limited usefulness.  Can we not document it and just print
it when we report the bison failure?  Should we just allow an environment
variable to over-ride it?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Reply via email to