From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Problems with pcc
Date: Mon, 12 Nov 2007 22:27:52 +0000 [thread overview]
Message-ID: <138db5d0129b86ff6bf1ea64d3f40864@terzarima.net> (raw)
In-Reply-To: <DF0C9771-131D-4719-8199-04B6C1080782@mac.com>
> mkfile
> What is _RESEARCH_SOURCE?
see /sys/doc/ape.ms (or pdf versions of it) for details and other things you might need anyway
> hoc.y
> You caught me there. I didn't even know I was breaking declarator
> rules!
> hoc.h
> See hoc.y above
C standards still insist on the annoying need for forward declarations.
if it has compiled on other compilers without fuss you should use better
compilers (or more likely many of the right -W options for gcc, but not too
many or it will moan about purely stylistic things!)
> init.c, math.c, symbol.c - no difference
> code.c
> I didn't know at the time that in a?b:c, both b and c have to be the
> same type
the usual arithmetic conversions apply (because the expression evaluates
to a single value of which ever type encompasses both true and false arms,
not values or non-values of two completely different types, such as a struct
and an int, or a void and anything else)
next prev parent reply other threads:[~2007-11-12 22:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 1:41 Pietro Gagliardi
2007-11-12 2:04 ` erik quanstrom
2007-11-12 14:17 ` Charles Forsyth
2007-11-12 14:24 ` erik quanstrom
2007-11-12 15:05 ` Charles Forsyth
2007-11-12 15:06 ` erik quanstrom
2007-11-12 17:43 ` Charles Forsyth
2007-11-12 20:52 ` Pietro Gagliardi
2007-11-12 22:27 ` Charles Forsyth [this message]
2007-11-16 10:19 ` Douglas A. Gwyn
2007-11-16 10:19 ` Douglas A. Gwyn
2007-11-16 19:46 ` Pietro Gagliardi
2007-11-19 10:15 ` Douglas A. Gwyn
2007-11-19 14:16 ` roland.kaufmann
2007-11-19 2:18 ` Pietro Gagliardi
2007-11-20 9:51 ` Douglas A. Gwyn
2007-11-19 2:22 ` Pietro Gagliardi
2007-11-20 9:51 ` Douglas A. Gwyn
2007-11-16 10:19 ` Douglas A. Gwyn
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=138db5d0129b86ff6bf1ea64d3f40864@terzarima.net \
--to=forsyth@terzarima.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).