From: Godmar Back (gback@cs.utah.edu)
Date: Wed Feb 03 1999 - 14:54:37 EST
>
> On Feb 3, 1999, Godmar Back <gback@cs.utah.edu> wrote:
>
> >> I'll try to dig the configure.in/acinclude.m4 code I wrote for japhar
> >> when I had commit privileges in their CVS tree, and I'll port them to
> >> Kaffe when I find the time for that.
>
> > Whatever. If you think that's better, do it that way.
> > If the current way of doing it breaks things, point out what it breaks
> > and we fix it.
>
> Well, I found the code, and it does something completely different
> from what I thought it did. But no problem, it's easy to work it out.
> But I'd like to understand why the BeOS port relies on those variables
> instead of using jtypes, which should accomplish the same. Since
> you've looked at the patches, I assume that you have a clue about
> what's the rationale for introducing these types... Care to explain?
> If you care, just tell me to go figure it out by myself, but then it
> will take longer :-)
>
As I understand it, the types get pulled in by seemingly harmless
includes such as <stdio.h> or <stdlib.h>.
So the question becomes how to avoid double definitions introduced by
gtypes.h.
What do you mean by "relies on those variables instead of using jtypes"?
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:56 EDT