From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pls. HELP porting problem
Date: Thu, 28 Apr 2005 23:10:05 -0700 [thread overview]
Message-ID: <56f675c169bbedc97d9f87fc4e683647@collyer.net> (raw)
In-Reply-To: <cc018ff1fabf2da3403adbdf6b786d8e@www2.mail.post.cz>
In C, writing the bare name of a function or array, say `foo', is
equivalent to writing &foo, so just delete the `&' if you want to
eliminate the warning.
next prev parent reply other threads:[~2005-04-29 6:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 5:53 pac7
2005-04-29 6:01 ` boyd, rounin
2005-04-29 6:10 ` geoff [this message]
2005-04-29 8:20 ` Charles Forsyth
2005-04-29 10:53 Aharon Robbins
2005-04-29 11:59 ` Bruce Ellis
2005-04-29 15:15 ` rog
[not found] ` <6ea05dc57c13d1df7359ec63990a0f8b@vitanuova.com>
2005-04-29 15:25 ` Bruce Ellis
2005-04-29 15:38 ` C H Forsyth
2005-04-29 16:09 ` Bruce Ellis
2005-04-29 12:31 ` Brantley Coile
2005-04-29 18:06 ` Ah Q
2005-04-30 9:03 ` Charles Forsyth
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=56f675c169bbedc97d9f87fc4e683647@collyer.net \
--to=geoff@collyer.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).