On 7 Jul 2001, Thayne Harbaugh wrote:
> I'm wondering where the TODO list is kept. It would be nice to
> enumerate all those minor things that need to be fixed but aren't
> serious enough to hold up 2.0:
See Brian's mail.
> should we use <inttypes.h> with a fallback?
This should be discussed before making a decission, because changing
all the datatypes through the whole code is going to deep in that
state. We should address this task _after_ the final release, ok?
> should the modules be more unifor? Some modules use FOOCONFFILE and
> FOOCONFDIR and pull them in in foo/init.c while other modules only use
> FOOCONFFILE. Some other differences as well that I have seen. Do we
> want the modules to be uniform?
That's true. Andy: What is more recent? The only FOOCONFFILE usage or
the combination of FOOCONFFILE and FOOCONFDIR?
My guess is the last one, because of the possibility of overriding
the internal confdir path under Win32 as this lines from
(libgii/gii/init.c) shows:
-----------------------------------------------------------
const char *giiGetConfDir(void)
{
#ifdef __WIN32__
/* On Win32 we allow overriding of the compiled in path. */
const char *envdir = getenv("GGI_CONFDIR");
if (envdir) return envdir;
#endif
return giiconfdir;
}
-----------------------------------------------------------
> A few other concerns that I can't recall because I didn't stuff them in
> a TODO file somewhere =^)
Well, when these small concerns won't break the build system again
then you can do that between 2beta4 and 2.0 final.
BTW: Thayne: I've committed the two patches I have sent you into CVS
plus did the same changes for libgalloc.
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
