[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Will ADT22Unix work for me again?
- Subject: Re: Will ADT22Unix work for me again?
- From: "mdj" <mdj.mdj@gmail.com>
- Date: 6 Mar 2007 04:34:05 -0800
- Complaints-to: groups-abuse@google.com
- In-reply-to: <45e95e99$0$91153$c30e37c6@lon-reader.news.telstra.net>
- Injection-info: s48g2000cws.googlegroups.com; posting-host=203.206.121.141; posting-account=W_jMEA0AAAAZdNaersJnc-7Hjv-SIC8Q
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- References: <45e95957$0$91145$c30e37c6@lon-reader.news.telstra.net> <45e95e99$0$91153$c30e37c6@lon-reader.news.telstra.net>
- User-agent: G2/1.0
- Xref: g2news2.google.com comp.sys.apple2:18227
On Mar 3, 9:40 pm, Tristan Mumford <xtristan.xmumf...@xgmail.xcom>
wrote:
> I fixed the warnings by adding string.h and stdlib.h to adt.c and adding
> string.h again to ucomm.c
>
> It still won't work for some reason.
The warnings are completely harmless - just there to remind you that
you've not included the correct ANSI C headers, which your fix fixes.
Like most C compilers gcc intrinsically recognises almost all the
symbols in the standard library, I think primarily since there is so
much old K&R style code that was written before the advent of function
protoypes, and C programmers tend to treat much of the standard
library as language native functionality.
Matt