[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] _get_output_format() signature MinGW 4

From: Vadim Zeitlin
Subject: Re: [lmi] _get_output_format() signature MinGW 4
Date: Wed, 22 Jun 2011 21:18:18 +0200

On Wed, 22 Jun 2011 17:38:20 +0000 Greg Chicares <address@hidden> wrote:

GC> "int" is what the author wrote in the article you cite below, but upon
GC> reflection it seems that it may always have been incorrect. Corrected
GC> 20110622T1736Z in revision 5213. (I'll change the 'skeleton' trunk
GC> later if necessary.)

 Thanks, this does solve the problem! The rest of this message is just for
completeness and can be safely ignored.

GC> >  But this is ugly and looking at the message referenced in the comment
GC> > above this function I see that apparently using this function is some sort
GC> > of a hack in the first place and that, quoting
GC> > http://article.gmane.org/gmane.comp.gnu.mingw.user/28747
GC> > 
GC> >   adding PRINTF_EXPONENT_DIGITS=2 to your environment remains 
GC> >   the preferred way to achieve this
GC> > 
GC> >  So maybe we could do this instead?
GC> As I understand it, that would need to be done in the end user's 
GC> not the developer's. Typical end users in corporations do not have 
GC> to modify the environment. And, even if they can, they might fail to, 
GC> the program to behave in a different way than we intend.

 I didn't explain myself clearly enough, sorry. I meant that we'd call
putenv("PRINTF_EXPONENT_DIGITS=2") on program startup ourselves. AFAICS
this should work too and I could test it if you're interested. OTOH, once
again, using "unsigned int" is a good enough solution for me so please just
don't reply if you are not and we'll leave it like this.

 Thanks for fixing this,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]