From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ca7e10a1e04455a1171c0a50ba873c14@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Thu, 28 Feb 2013 14:15:12 +0000
To: 9fans@9fans.net, jas@corpus-callosum.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] X11
Topicbox-Message-UUID: 20f17b00-ead8-11e9-9d60-3106f5b1d025

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