strtod endptr bytes reversed?

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There is a post from 2001 that says the high and low bytes of the endptr for the strtod function are reversed.

"strtod returns wrong endptr"

Are they still reversed? It looks like it is. I am using the endptr for error detection and am having a lot of trouble. Could something else be wrong? I installed WinAvr in, I think, December of 2004.

Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Uhg, ok, so strtod returns with the same no conversion performed condition if the input string is'0', '0.0', '0e0' or 'cupcake'. But the string '0e1' returns with a conversion complete condition. It looks like the string still must be checked for valid input before it is passed to strtod. Is this right?

Thanks again.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Please file a bug report for this.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The bugs are entered here https://savannah.nongnu.org/bugs... Is this the right place? The two problems are in separate bug reports. Thanks again, I wish I could help fix it.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I loaded the WinAVR-20050214 release and the swapped bytes in the endptr has been fixed! Excellent. The other problem of strtod returning an error condition for an input of 0.0 still exists. The comments for the bug now reflect this but the bug is still open. Can anyone close a bug or does it need to be assigned first?