Re: [pgsql-hackers-win32] snprintf causes regression tests to fail - Mailing list pgsql-hackers

From Nicolai Tufar
Subject Re: [pgsql-hackers-win32] snprintf causes regression tests to fail
Date
Msg-id d809293905031011225ff257c9@mail.gmail.com
Whole thread Raw
In response to Re: [pgsql-hackers-win32] snprintf causes regression tests  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [pgsql-hackers-win32] snprintf causes regression tests
List pgsql-hackers
On Wed, 9 Mar 2005 22:51:27 -0500 (EST), Bruce Momjian
<pgman@candle.pha.pa.us> wrote:
> > What do you think about it? Shall I abandon FreeBSD and go ahead
> > Incorporating Trio?
>
> Yes, maybe just add the proper %$ handling from Trio to what we have
> now.

Adding proper %$ from Trio will require too much effort. I would
rather not do it. Not because I am lazy but because:

1) Trio team seem to be very serious about standards, update
the library as soon as new standards come out:
<quote>
Trio fully implements the C99 (ISO/IEC 9899:1999) and UNIX98 (the
Single Unix Specification, Version 2) standards, as well as many
features from other implementations, e.g. the GNU libc and BSD4.
</quote>

2) If we integrate the whole library in source code we will
not have to maintain it and will rely on Trio team for bug fixes
and updates. Integrating it will be very easy since all of the
functions begin with "trio_". I used it instead of the src/port/snrpintf.c
one and it passes regression tests under Win32 just fine.

The downside is that Trio library is rather big. It is 3 .c and 6 .h
files totalling 11556 lines. Compiled it is 71224 bytes not stripped
and 56204 bytes stripped on Solaris 10 for x86, 32-bit. Even for
a shared library it will probably be too much. Trio has a lot
of string handling functions which are probably not necessary.
Would you like me to try to remove everything unnecessary from
it or we will settle with the full version?


Regards,
Nicolai Tufar

pgsql-hackers by date:

Previous
From: "Barry Lind"
Date:
Subject: Re: We are not following the spec for HAVING without GROUP BY
Next
From: Michael Fuhr
Date:
Subject: Re: [BUGS] We are not following the spec for HAVING without