zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk, martin.ebourne@arcordia.com
Subject: Re: New options & arguments processing system for ZSH
Date: Sun, 19 Aug 2001 05:40:05 +0000	[thread overview]
Message-ID: <1010819054006.ZM16192@candle.brasslantern.com> (raw)
In-Reply-To: <OF653C664E.8AB47B26-ON80256AAB.004AC761@uk.jpmorgan.com>

On Aug 17,  2:59pm, martin.ebourne@arcordia.com wrote:
}
} For now I'd like any comments people have, especially bug reports and
} praise (yeah right!).

I've barely glanced over it, but my initial impressions are:

- I like it a lot better than the XML version suggested by Felix, but
  the ideal solution probably lies somewhere between the two.

- It suffers from the same problems as my _arg_compile scheme, to wit,
  every function that uses it has to do a lot of extra work that is not
  directly related to the purpose of the function.

- Here-documents end up getting encoded as strings in the compiled
  function definition in memory, so this is probably prohibitive for
  general use except when using zcompile'd files with memory mapping.

- You should have sent it to zsh-workers, not zsh-users. :-)

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


       reply	other threads:[~2001-08-19  5:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF653C664E.8AB47B26-ON80256AAB.004AC761@uk.jpmorgan.com>
2001-08-19  5:40 ` Bart Schaefer [this message]
2001-08-20  6:53 Felix Rosencrantz
2001-08-20  7:06 ` Borsenkow Andrej
2001-08-20 10:42 martin.ebourne
2001-08-21 13:50 ` Felix Rosencrantz
2001-08-20 11:17 martin.ebourne
2001-08-21 14:07 martin.ebourne
2001-08-24  6:13 ` Felix Rosencrantz

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=1010819054006.ZM16192@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=martin.ebourne@arcordia.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).