| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
| From: | Kbwms AT aol DOT com |
| Message-ID: | <1ea.12cf40ab.2ce008fe@aol.com> |
| Date: | Sun, 9 Nov 2003 16:17:50 EST |
| Subject: | Re: C99 Functions Under Development and Checkout |
| To: | djgpp-workers AT delorie DOT com |
| MIME-Version: | 1.0 |
| X-Mailer: | 8.0 for Windows sub 6021 |
| Reply-To: | djgpp-workers AT delorie DOT com |
--part1_1ea.12cf40ab.2ce008fe_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit What should we do about the functions in libm that fall under the purview of C99? Should they be modified to bring them into compliance with C99? --part1_1ea.12cf40ab.2ce008fe_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable <HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D3 FAMILY=3D"SERIF" FACE=3D"= Georgia" LANG=3D"0">What should we do about the functions in libm that fall=20= under the purview of C99? Should they be modified to bring them into c= ompliance with C99?</FONT></HTML> --part1_1ea.12cf40ab.2ce008fe_boundary--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |