RE: [Firebird-devel] win32 build... parse.c

[Claudio V. C. <cv...@us...>]

> -----Original Message-----
> From: fir...@li...
> [mailto:fir...@li...]On Behalf Of reed
> mideke
> Sent: Jueves 2 de Agosto de 2001 21:21
> >
> It is also in sys/cdefs.h (on my linux, anyway). Some BS for
> platforms that don't support prototypes.

Any idea which platforms still don't support prototypes, assuming we are
writing about C function prototypes? I tend to think that yacc might be too
conservative here.

> > > Using bison doesn't work, because bison does things like

It was reported earlier by at least 3 people that bison won't work because
it puts the code in other order in the generated C file, so the functions
that are defined in parse.y won't be defined before being called.


> There's a couple of others, but that would solve the immediat
> problem with bison. The other question is why parse.c needs
> windows.h
> I haven't looked at it in detail, but my guess is that it is
> only for some debug output, since it is only included in debug
> builds.

I put that line there and if you delete it, I will wipe out you!
:-)
It's used to be able to load/unload the debug console dynamically in
Windows. I needed some function defined in this header. More sbout it in my
reply to Sean.
For understandable reasons, the debug console is not available in prod
builds.


> > The problem with one approved yacc for checkins is that yacc might not
> > exist in its approved form on all platforms.  parse.y and parse.c could
> > easily get out of sync.
> >
> > The problem with not keeping parse.c in the source tree is certain
> > platforms (ex. win32) don't come with a version of yacc that can handle
> > parse.y.  Claudio said he had quite an adventure finding the correct
> > yacc.

Yes, this was my experience. And this wasn't the only tool that gave me
headaches. I wasted a couple of hours finding other utilities just to have
all ones that are called from the auxiliary programs. If I remember well,
either the program that generates the "codes" files or the one that
generates the msg file calls MV. Well, it turns out that something as simple
as MV didn't work well in the ports I picked, so again I had to find a third
variant. I explained to one of the authors what was failing in the source
code (IMHO) and he fixed the utility.


> I'm thinking that the yacc that claudio found should be
> available for people who want to build on win32.
>
> (claudio can you send me the URL or the .exe ?)

Maybe, but remembering which of the ones that I got is the one I unzipped
will be another adventure, be patient, please. I seem to remember the
license said the package had to be exposed complete, not the only file.

We need to name a coordinator in charge of an official parse.c.
:-)

C.