Frank Schroeder MHF-sl wrote:
I have tried to convert an unsigned long int to ascii using the function
char * ultoa (unsigned long int __val, char *__s, int __radix) of
stdlib.h.
This function converts only the lower two bytes of the unsigned long,
like it were a normal unsigned.
yep, that is
You make need to write the line as:
ultoa(10UL,dummytext,10);
I've had the compiler complain about overflows (when I multiplied 2 constants
together to make a long constant) where the constant was cast just fine using
another compiler.
Dale
Frank Schroeder MHF-sl wrote:
Hello,
I have t
Hello,
I have tried to convert an unsigned long int to ascii using the function
char * ultoa (unsigned long int __val, char *__s, int __radix) of
stdlib.h.
This function converts only the lower two bytes of the unsigned long,
like it were a normal unsigned.
I have tried with this line:
ultoa((uns
Ya, I didn't want the extra '*', that was just a typo.
Thanks for the info on the sprintf, is there any plan for float support? Seems
silly
there is support for float as a general use data type, but not in sprintf.
BTW, I forgot to tell you earlier, typecasting gets rid of the warning, but not
Hi Steve,
Yes, there are some piacularities with 4.0... But it seems that the code looks
smaller, especially when no long or long long operations exist.
cheers,
~d
On Thursday 25 August 2005 02:28, Steve Underwood wrote:
> How does the code produced by GCC 4.xx look? GCC 3.2.3 seems to do
> bet
