From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1d5d51400603141017p2c79a51em59e32b3f9b55ce18@mail.gmail.com> Date: Wed, 15 Mar 2006 02:17:48 +0800 From: "Fernan Bolando" To: 9fans@cse.psu.edu Subject: Re: [9fans] porting linux program for beginners In-Reply-To: <4801e8bace9bf2d0ff5a01dd57bf1a79@vitanuova.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1d5d51400603140804m72eddf8jd4474a9f7ef0b23c@mail.gmail.com> <4801e8bace9bf2d0ff5a01dd57bf1a79@vitanuova.com> Topicbox-Message-UUID: 13f9b84c-ead1-11e9-9d60-3106f5b1d025 On 3/15/06, C H Forsyth wrote: > the compiler shows the linear type representation it uses internally. > IND is `indirect', a pointer, or * > UCHAR is `unsigned char' > CONST is obviously `const' > so in > > dumb_input.c:249[stdin:1718] argument prototype mismatch "IND UCHAR" for = "IND CONST CHAR": strlen > > you're passing an unsigned char* to strlen, which expects const c= har* (or char*) > > the compiler could possibly translate them back to normal C declarator fo= rm > from the internal one, but on the other hand, in more subtle cases, > seeing them written in linear form can be helpful if you've got > a * or () in the wrong place. > > newer versions of gcc will object too, > so you might as well get the types right now. thanks. it is ok now. I will see if I can get some of my codes posted on my webpage this weekend It will is mostly some simple ape ports and I am not sure if there is any real advantage to port it as a native plan9 program. -- Public PGP/GnuPG key (http://www.fernski.com) pub 1024D/3576CA71 2006-02-02 Fernan Bolando Key fingerprint =3D FDFE C9A8 FFED C1A5 2F5C EFEB D595 AF1C 3576 CA71