From: "EBo" <ebo@sandien.com>
To: "erik quanstrom" <quanstro@quanstro.net>, <ebo@sandien.com>,
<9fans@9fans.net>
Subject: Re: [9fans] compiler warnings for libavl/avl.c
Date: Tue, 2 Mar 2010 11:41:03 -0700 [thread overview]
Message-ID: <twig.1267555263.12166@swcp.com> (raw)
In-Reply-To: <0d7eca13df84b4712c896f255f4f9285@brasstown.quanstro.net>
erik quanstrom <quanstro@quanstro.net> said:
> how about changing 9c so you don't get this warning?
At the moment the compiler is set to report all warnings (-Wall). I would
rather ignore these two warnings then turn the warnings off.
Out of curiosity is there a reason why the subroutines should not be declared
void walkavl... instead of static void walkavl? I understand that removing
the static declaration puts the two subroutines in question into global
namespace when linking to libavl.
I did a quick check and removing the static declaration removed the warnings,
and plan9port built without incident.
I hope I am not being annoying, I really am trying to get a sense of the
communities coding and process standards.
Thanks and best regards,
EBo --
next prev parent reply other threads:[~2010-03-02 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 9:43 [9fans] Has Anyone compiled 9vx on snow leopard ? prem
2010-02-26 15:16 ` Oleg Finkelshteyn
2010-03-02 17:02 ` [9fans] compiler warnings for libavl/avl.c EBo
2010-03-02 17:12 ` erik quanstrom
2010-03-02 17:40 ` EBo
2010-03-02 17:50 ` Edward E Elzey
2010-03-02 17:52 ` erik quanstrom
2010-03-02 18:41 ` EBo [this message]
2010-03-04 18:10 ` Russ Cox
2010-03-01 9:49 ` [9fans] Has Anyone compiled 9vx on snow leopard ? prem
2010-03-01 9:49 ` prem
2010-03-01 10:30 ` John Stalker
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=twig.1267555263.12166@swcp.com \
--to=ebo@sandien.com \
--cc=9fans@9fans.net \
--cc=quanstro@quanstro.net \
/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).