From: "Fernan Bolando" <fernanbolando@mailc.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] porting linux program for beginners
Date: Wed, 15 Mar 2006 02:17:48 +0800 [thread overview]
Message-ID: <1d5d51400603141017p2c79a51em59e32b3f9b55ce18@mail.gmail.com> (raw)
In-Reply-To: <4801e8bace9bf2d0ff5a01dd57bf1a79@vitanuova.com>
On 3/15/06, C H Forsyth <forsyth@vitanuova.com> 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
prev parent reply other threads:[~2006-03-14 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 16:04 Fernan Bolando
2006-03-14 16:08 ` andrey mirtchovski
2006-03-14 16:27 ` C H Forsyth
2006-03-14 16:47 ` David Leimbach
[not found] ` <4801e8bace9bf2d0ff5a01dd57bf1a79@vitanuova.com>
2006-03-14 18:17 ` Fernan Bolando [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d5d51400603141017p2c79a51em59e32b3f9b55ce18@mail.gmail.com \
--to=fernanbolando@mailc.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).