From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE select() and awkward Python subprocess PIPEfitting
Date: Tue, 26 Feb 2013 10:17:38 -0600 [thread overview]
Message-ID: <000D9528-3D1D-453D-8795-4FF92DE2D2D6@corpus-callosum.com> (raw)
In-Reply-To: <CAOw7k5i-riwQov3w_pDfeG469rrgTkEUkYLnvusSz=YF9cUkwg@mail.gmail.com>
On Feb 26, 2013, at 5:41 AM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> In other words, I'd fix select, and then change whatever else needs to be changed (if anything does) if X11 then stops working.
If I'm interpreting this correctly, as well as the select() code,
then by removing that block from the "ensure buffered" loop the
slot selection loop should work as intended and return if any
error or read fds are ready.
It is possible that _buf.c:327 may be incorrect for actually
handling an error. This requires some additional setup and
testing before being able to be proven. I'm also looking for
additional APE examples that actually use select() to see if
there are any other changes required. So far I've only found
Python and X11.
If someone has X11 and wants to test this change w/o completely
replacing /$objtype/lib/ape/libap.a, drop the edited _buf.c file
into your X11 source and add _buf.$O to your mkfile w/
pcc -c -I/sys/src/ape/lib/ap/plan9 -D_POSIX_SOURCE -D_PLAN9_SOURCE -D_BSD_EXTENSION _buf.c
-jas
next prev parent reply other threads:[~2013-02-26 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 2:29 Jeff Sickel
2013-02-26 5:53 ` Jeff Sickel
2013-02-26 11:25 ` Yaroslav
2013-02-26 11:41 ` Charles Forsyth
2013-02-26 16:17 ` Jeff Sickel [this message]
2013-02-26 15:29 ` Jeff Sickel
2013-02-26 16:20 ` Charles Forsyth
2013-02-26 16:26 ` Charles Forsyth
2013-02-26 17:01 ` Jeff Sickel
2013-02-26 18:36 ` Charles Forsyth
2013-02-26 16:48 ` Anthony Sorace
2013-02-26 18:25 ` Jeff Sickel
2013-02-27 2:03 ` Federico G. Benavento
2013-02-27 15:03 ` Jeff Sickel
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=000D9528-3D1D-453D-8795-4FF92DE2D2D6@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.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).