From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: zselect builtin.
Date: Wed, 08 May 2002 10:59:05 +0100 [thread overview]
Message-ID: <8259.1020851945@csr.com> (raw)
In-Reply-To: "Borsenkow Andrej"'s message of "Wed, 08 May 2002 09:36:55 +0400." <6134254DE87BD411908B00A0C99B044F02E89A66@mowd019a.mow.siemens.ru>
Borsenkow Andrej wrote:
> If we start adding low-level system interface I really wish that we
>
> - put it in separate module (like Perl POSIX)
> - or at least under own hierarchy (like zsh/POSIX/select)
>
> In which case it would be nice (as Bart already suggested) to have
> standard name pattern; posix_select or sys_select (depending upon level
> of system independency we are aiming at).
It's too late: we have stat, the files module, and various other bits
which talk to the system in other ways like TCP. Unless we want to move
everything around now, I don't see a good reason for putting this
anywhere special. (`stat' already clashes with various external
commands which do a similar job, unfortunately.) Until then, separate
modules for each separate interface seems to me the cleanest way
forward.
Why is `posix_select' or `sys_select' an improvement over our current
mini-convention with the `z', which also covers things which aren't
strictly tied to system calls? To me, anyway, it implies a greater
tie-in to the underlying system call than you get with the shell builtin
--- no fd sets, no maximum fd, no errno handling. This is a distinct
difference from perl, which tries to emulate the POSIX interface as
closely as possible in such cases.
(By the way, there was an interesting note on the Austin group list today
that the `error' fd's in the select call are really for exceptions, and
the only one currently defined is out-of-band data on a socket. I may
point this out, since most select manual pages don't.)
> Aso you probably can't fully utilize select without non-blocking I/O.
I don't see this; you can already poll a blocking fd using a zero
timeout. But some fcntl interface is certainly a possibility.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next prev parent reply other threads:[~2002-05-08 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 11:25 Peter Stephenson
2002-05-07 14:46 ` Bart Schaefer
2002-05-07 17:01 ` Peter Stephenson
2002-05-07 19:01 ` Bart Schaefer
2002-05-08 5:36 ` Borsenkow Andrej
2002-05-08 9:59 ` Peter Stephenson [this message]
2002-05-08 15:55 ` Bart Schaefer
2002-05-12 10:42 ` Borsenkow Andrej
2002-05-14 9:18 ` Oliver Kiddle
2002-05-08 13:26 ` Peter Stephenson
2002-05-08 13:37 ` PATCH: zselect bug, already Peter Stephenson
2002-05-08 15:34 ` Module loading by name (Re: PATCH: zselect builtin.) Bart Schaefer
2002-05-08 17:23 ` PATCH: zselect builtin Peter Stephenson
2002-05-08 17:49 ` Peter Stephenson
2002-05-13 9:06 ` Sven Wischnowsky
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=8259.1020851945@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).