zsh-users
 help / color / mirror / code / Atom feed
From: TGAPE! <tgape@cyberramp.net>
To: zsh-users@math.gatech.edu
Subject: Re: Perl and ZSH
Date: Sat, 18 Apr 1998 09:53:45 +0000 (GMT)	[thread overview]
Message-ID: <199804180953.JAA08829@dal-tsa19-60.cyberramp.net> (raw)
In-Reply-To: <Pine.GSO.3.93.980418124955.8290C-100000@atle> from "Jonas Bofjall" at Apr 18, 98 12:53:25 pm

Jonas Bofjall wrote:
> On Fri, 17 Apr 1998 tep@colltech.com wrote:
> 
>> I've actually been tinkering with the idea of embedding a Perl
>> interpreter inside ZSH but I got stumped when it came time to
> 
> zsh is good because it keeps the executables size within bounds even
> while having all these features. But Perl is *complex*... Wouldn't it
> be time to modularize zsh some? And I don't mean autoloading of shell
> script functions but of compiled code.

First, I seem to recall hearing something about that already.  Second,
no.  Do not encourage them.  Perl is embeded *enough*, simply by it
being a unix shell.  If I need the power of perl, I'd rather write a
perl script.  I realize a powerful shell can be nice, but there is
something called sanity which must be kept track of.

I'm actually of the opinion that the zshexpn is possibly getting a
little too complete - benchmarking shows that find is better suited for
most complex tasks.  That having been said, I do find virtually every
feature of zshexpn useful, so long as you use them within reason.
Remember that find still exists, and is better for the major endevor.

Perl is not only complex, but it's a fairly efficient piece of code.  It
could be improved significantly, but I don't believe the people who are
talking about putting it in zsh will necessarily have the time or
patience to even match its efficiency.

All this having been said, I wouldn't complain too loudly over an
optional perl expression parser, though I'd like it to be a compile time
option.

>On 17 Apr 1998, Karsten Thygesen wrote:
>
>> another project. We have a lot of resources available to projects like
>> Infoseek searchengine, newsgroups (if that is prefered over
>> mailinglists) and even CVS servers for distributed development.
>
>btw is there a cvs repository for zsh?

Not that I know of[1]; what's wrong with RCS?  You have it on your
system if you have CVS.  Since CVS uses RCS to do its work, it should be
trivial to convert.  Unfortunately, I've just shared pretty much my sum
total knowledge of CVS...

Ed

[1] Though Bart Schaefer might know better.


  reply	other threads:[~1998-04-18 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-17 19:56 backing up with zsh Sven Guckes
1998-04-17 20:20 ` Rob Windsor
1998-04-18  9:36   ` TGAPE!
1998-04-18 18:08     ` Bart Schaefer
     [not found] ` <vkzphkchu4.fsf@cdc.noaa.gov>
1998-04-17 20:42   ` Sven Guckes
     [not found]     ` <vkyax4cgur.fsf@cdc.noaa.gov>
1998-04-17 21:00       ` Sven Guckes
1998-04-18  0:44         ` Perl and ZSH (WAS: Re: backing up with zsh) tep
1998-04-17 21:24           ` Bart Schaefer
1998-04-18 10:53           ` Perl and ZSH Jonas Bofjall
1998-04-18  9:53             ` TGAPE! [this message]
1998-04-18 18:21               ` Bart Schaefer
1998-05-04 23:47                 ` Zsh and CVS Scott RoLanD
1998-04-18 10:13     ` backing up with zsh Mirar
1998-04-20  8:47     ` Andrew Main

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=199804180953.JAA08829@dal-tsa19-60.cyberramp.net \
    --to=tgape@cyberramp.net \
    --cc=zsh-users@math.gatech.edu \
    /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).