This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: strtoll() and strtoull()
- To: khan at thor dot xraylith dot wisc dot edu
- Subject: Re: strtoll() and strtoull()
- From: Juergen Schoenwaelder <schoenw at ibr dot cs dot tu-bs dot de>
- Date: Fri, 1 Oct 1999 10:07:57 +0200
- CC: cygwin at sourceware dot cygnus dot com
- References: <199909301705.MAA10463@mercury.xraylith.wisc.edu>
>>>>> Mumit Khan writes:
Mumit> If you do mean strtoll/strtoull (ie., *two* l's at the end),
Mumit> these are not in any standard I know of. If the two 'l's at the
Mumit> end refer to the long long version, those are non-standard and
Mumit> newlib doesn't implement it. Newlib maintainers will accept
Mumit> patches of course.
Of course, I mean strtoll/strtoull. And they are at least very close
to standard. Besides that, they make a whole lot of sense since the
gcc supports long long and friends.
Anyway, is it legal to simply copy the implementation of strtoll() and
strtoull() from glibc? Or do you have to implement it from scratch for
some reason?
/js
--
Juergen Schoenwaelder Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de> Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com