[Patches] [ python-Patches-419651 ] Metrowerks on Mac adds 0x itself

[noreply@sourceforge.net]

Patches item #419651, was updated on 2001-04-27 15:22
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=419651&group_id=5470

Category: core (C code)
Group: 2.0.1 bugfix
Status: Open
Resolution: None
Priority: 5
Submitted By: Jack Jansen (jackjansen)
Assigned to: Tim Peters (tim_one)
Summary: Metrowerks on Mac adds 0x itself

Initial Comment:
The Metrowerks C library on the Mac already prints 0 as 0x0 so don't add another 0x to the front of 
that.


----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2001-04-27 16:40

Message:
Logged In: YES 
user_id=31435

Section 7.9.6.1 ("The fprintf function"), under the 
description of the "#" flag character: "For x (or X) 
conversion, a nonzero result will have Ox (or 0X) prefixed 
to it."

In the meantime, at least one other box is known that 
screws this up, and I said at the time that if a second box 
ever appeared, I'd do something about it <wink>.

----------------------------------------------------------------------

Comment By: Jack Jansen (jackjansen)
Date: 2001-04-27 15:42

Message:
Logged In: YES 
user_id=45365

There's a patch now. Silly form wanted me to check the box, even though I had used the attach button:-(

I'll also send the bug report to metrowerks, but that'll be a looooong time in fixing, I guess. Do you (or anyone 
else) happen to have a section number/etc for the requirement?


----------------------------------------------------------------------

Comment By: Jack Jansen (jackjansen)
Date: 2001-04-27 15:40

Message:
Logged In: YES 
user_id=45365




----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-04-27 15:32

Message:
Logged In: YES 
user_id=31435

Jack, there's no patch here.

Have you reported this bug to Metrowerks?  The C std is 
very clear that a %#x format must *not* produce a leading 
0x when and only when the number being converted is 0.  
This isn't a debatable issue:  if they're producing 0x0, 
they're wrong.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=419651&group_id=5470