| delorie.com/archives/browse.cgi | search |
| Date: | Mon, 10 Apr 2000 21:34:50 -0400 |
| Message-Id: | <200004110134.VAA05635@envy.delorie.com> |
| From: | DJ Delorie <dj AT delorie DOT com> |
| To: | djgpp AT delorie DOT com |
| In-reply-to: | <002301bfa351$9c3bb3a0$2d9709ca@saraswati> |
| (bharatmallapur AT eth DOT net) | |
| Subject: | Re: Ansi/iso C compliance whatever it may eventually mean |
| References: | <002301bfa351$9c3bb3a0$2d9709ca AT saraswati> |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
> in short i want to know that how is it that gcc which is supposed to be > "totally" ansi/iso compliant not have getchar which is a standard library > function.The use of getchar in K&R 2 and in many ansi compliant programs > seems to be enough to call it ansi-compliant. > The fact is i decided to download djgpp only after being told on comp.lang.c > that it is a fully ansi/iso compliant compiler and of course that it is > free. > So now please tell me whether djgpp is ansi/iso C compliant or not. The key is "supposed to be". You may have found a bug. If so, please fix it. The sources are in v2/djlsr203.zip. TANSTAAFL.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |