Re: [HACKERS] bison

From: wieck(at)debis(dot)com (Jan Wieck)
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas Lockhart)
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, peter_e(at)gmx(dot)net, pgsql-docs(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] bison
Date: 1999-10-15 10:18:24
Message-ID: m11c4RM-0003kLC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

>
> > >> You might want to include into the installation instructions (or whereever
> > >> it will end up) that GNU bison 1.25 is required. (right after the flex
> > >> stuff)
> > > We haven't been careful about building and shipping the bison output
> > > in the tarball distribution, as we have for the main parser.
> > Huh? src/tools/release_prep automatically builds both the main parser
> > and ecpg bison output files. Is there other stuff it should be
> > handling too?
>
> afaik some of Jan's language stuff uses yacc also...

Yepp - PL/pgSQL has it's own scanner/parser (i.e.
flex/bison). The tricky part in this case is that the
languages object file will be loaded at runtime into the
backend, where the main scanner/parser is already present.
Thus I'm mangling with sed(1) over the generated sources to
avoid global symbol conflicts.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bill Atwood 1999-10-15 15:35:51 subscribe
Previous Message Thomas Lockhart 1999-10-15 04:33:32 Re: [HACKERS] bison

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 1999-10-15 10:20:15 Re: [HACKERS] Scripts again
Previous Message Peter Eisentraut 1999-10-15 09:36:35 Re: [HACKERS] Scripts again