On Tue, Mar 09, 2004 at 01:45:59PM +0800, Jonathan Wilson wrote:
> >Discovered an issue with null pointer passed for %s (Warcraft III likes to
> >do that it seems). I handle it by printing "(null)". Other than that, it
> >will
> Have you made it do something usefull if the user passes a null f
On Mon, Mar 08, 2004 at 08:28:38PM +0100, Joerg Mayer wrote:
> Ethereal brings its own version of (v)snprintf in form of the snprintf.[hc]
> files. While Ethereal is GPLed, the files in question are LGPLed. The
> files do not originate with Ethereal but I don't remember where they
> came from.
>
On Mon, Mar 08, 2004 at 10:15:33AM -0800, Alexandre Julliard wrote:
> Probably 3), but I don't think you want to start with the glibc code,
> it's fairly ugly code, with many dependencies on glibc internals and
> gcc-specific things. Hopefully we can find a more portable
> implementation somewhere
On March 8, 2004 10:54 am, Bill Medland wrote:
> On March 8, 2004 10:15 am, Alexandre Julliard wrote:
> > Mike Hearn <[EMAIL PROTECTED]> writes:
> > > On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote:
> > >> 1) Create our own vsnprintf version from scratch (fairly difficult)
> > >> or
> > >
On March 8, 2004 10:15 am, Alexandre Julliard wrote:
> Mike Hearn <[EMAIL PROTECTED]> writes:
> > On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote:
> >> 1) Create our own vsnprintf version from scratch (fairly difficult)
> >> or
> >> 2) Create a wrapper for glibc's vsnprintf that translate
On Mon, Mar 08, 2004 at 10:48:31AM +, Mike Hearn wrote:
> On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote:
> > 1) Create our own vsnprintf version from scratch (fairly difficult)
> > or
> > 2) Create a wrapper for glibc's vsnprintf that translates win32ish format
> > statements into
Mike Hearn <[EMAIL PROTECTED]> writes:
> On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote:
>> 1) Create our own vsnprintf version from scratch (fairly difficult)
>> or
>> 2) Create a wrapper for glibc's vsnprintf that translates win32ish format
>> statements into a glibc friendly one. (n
On Mon, 08 Mar 2004 11:59:55 +0100, Uwe Bonnes wrote:
> Another option is to extend the glibcv version and try to get that version
> into glibc...
a) It's not portable to non-glibc systems then
b) I take it you never tried to get patches into glibc before ;)
I mean if you think you can convince U
> "Mike" == Mike Hearn <[EMAIL PROTECTED]> writes:
Mike> On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote:
>> 1) Create our own vsnprintf version from scratch (fairly difficult)
>> or 2) Create a wrapper for glibc's vsnprintf that translates win32ish
>> format statements i
On Sun, 07 Mar 2004 19:32:39 -0700, Jesse Allen wrote:
> 1) Create our own vsnprintf version from scratch (fairly difficult)
> or
> 2) Create a wrapper for glibc's vsnprintf that translates win32ish format
> statements into a glibc friendly one. (not too bad and smaller patch) We
> could lat
Hi,
Here I have filed a bug on vsnprintf:
http://bugs.winehq.org/show_bug.cgi?id=2075
Basically it says, without repeating, that vsnprintf called from glibc is not
quite a suitable replacement for an actual msvcrt vsnprintf. An example is
given to highlight a specific issue. I have a question
11 matches
Mail list logo
