On 3/15/06, C H Forsyth <[EMAIL PROTECTED]> 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 char* > (or char*) > > the compiler could possibly translate them back to normal C declarator form > 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 = FDFE C9A8 FFED C1A5 2F5C EFEB D595 AF1C 3576 CA71
