From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net, jas@corpus-callosum.com
Subject: [9fans] X11
Date: Thu, 28 Feb 2013 14:15:12 +0000 [thread overview]
Message-ID: <ca7e10a1e04455a1171c0a50ba873c14@quintile.net> (raw)
I have rebuilt equis with the change in ape's select
and it seems to work fine (tested with xlock and xterm only).
this was not quite straightforward due to changes in ape, and
the compiler becomming a little stricter.
On this subject, what is the general feeling on integer
type'ed functions which call exit() before falling off the
end of the function?
This is fairly common in X11 and I have just added a return 0 on
the end to push the code through the compiler, but should the
compiler be taught about this case?
if so, it gets a bit nasty as this feature is named
exit() under ape and exits() in native plan9.
Personally I think falling of the end of a function
is a bug and should be fixed, but perhaps it should
just be a warning rather than an error to make
building foreign code simpler.
-Steve
next reply other threads:[~2013-02-28 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 14:15 Steve Simon [this message]
2013-02-28 14:21 ` Charles Forsyth
2013-02-28 17:19 ` dexen deVries
2013-02-28 18:10 ` Joel C. Salomon
2013-02-28 19:46 ` Steve Simon
2013-03-01 4:11 ` Federico G. Benavento
2013-03-01 13:05 ` Comeau At9Fans
2013-02-28 23:02 ` [9fans] X11 [was APE select and awkward Python subprocess PIPEfitting] Jeff Sickel
2013-02-28 23:13 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 23:39 [9fans] x11 treilov
2004-06-03 8:56 ` plan9
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=ca7e10a1e04455a1171c0a50ba873c14@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
--cc=jas@corpus-callosum.com \
/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).