zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: zselect builtin.
Date: Wed, 08 May 2002 14:26:44 +0100	[thread overview]
Message-ID: <21268.1020864404@csr.com> (raw)
In-Reply-To: "Peter Stephenson"'s message of "Tue, 07 May 2002 12:25:15 BST." <17029.1020770715@csr.com>

Peter Stephenson wrote:
> Here's a builtin to act as a front end to a `select' system call.

I've committed this, with subtle changes over the form I posted mostly as
indicated in previous postings.  I've added `-A assoc' for associative
array handling.

It's still called zselect, and still lives in zsh/zselect.  I'm happy to
consider more logical overall naming, but until then I don't see any
point in introducing new conventions piecemeal.  (Another argument
against tying the name more closely to the system call is that it is
possible and probably useful to provide an alternative implementation
based on poll().)

Warning:  I used this overnight as part of a test and there seems to be
a memory leak somewhere, not necessarily zselect itself (where I can't
see where it would be).  I was using ztcp, but it was the same TCP
connection all the time, so I don't think that's it either.  It's just
possible I was accumulating some humongous array, but I couldn't see
where that would have been, either.  Unfortunately I had to kill the
shell because I made it uninteruptible.

Another note: the zmodload manual page is written to imply that having a
module name the same as a builtin, or other autoloadable entity, is
useful.  As far as I can see, this is never the case now, due to the
hierarchical naming.  It might be better to remove this feature or at
least add implied aliasing into the zsh/* name segment when there's only
one argument.  (You can add module aliases by hand, but it takes away
the point of the shortcut.)

-- 
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.
**********************************************************************


  parent reply	other threads:[~2002-05-08 13:27 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
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 [this message]
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=21268.1020864404@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).