From: Vincent Stemen <zsh@hightek.org>
To: zsh-users@sunsite.dk
Subject: Re: Python/zsh/perl [was: named directory expansion on strings]
Date: Sun, 14 Mar 2004 15:57:00 -0600 [thread overview]
Message-ID: <20040314215700.GA61154@quark.hightek.org> (raw)
In-Reply-To: <1040314185437.ZM6792@candle.brasslantern.com>
On Sun, Mar 14, 2004 at 06:54:37PM +0000, Bart Schaefer wrote:
> On Mar 13, 6:48pm, Thorsten Kampe wrote:
> : | print ${(r.$JUSTIFY.):-"${ltred}! ${white}..."
>
> You don't need $JUSTIFY there: (r.JUSTIFY.) is sufficient, because the
> expression is interpreted in math context where all non-keywords are
> variable references.
>
> : Long live the Zen of Python[2].
>
> Hrm. As far as I'm concerned, the Python folks went wrong when they gave
> semantic significance to depth of whitespace indentation, and all of the
> right decisions they've made since have been a waste of effort.
I agree. This surprising discovery is the primary reason I never put
any serious consideration into learning Python. Seems like it would
be a nightmare to fix if you get your indentation messed up (which is
extremely common when juggling code around). Also, I use the auto
indentation features of xemacs all the time. I see no way you could
do that without code block delimiters. Seems like a step backward in
time.
As long as I am here, I thought I would use the opportunity to give
you Z shell developers some more positive feedback :-).
I was very pleased to find that you can do direct array indexing of
single dimensional arrays in zsh. ie. if x=abcd, then $x[2] = b.
That very feature is most commonly the weakness of tradition shell
script and even Perl that sometimes ends up causing me to write a
routine as an external C program when I am writing a complex script.
As wonderful of a language as Perl is, that is the one limitation I
have found that gives Z shell an advantage, even over Perl, in
situations where that lower level control is needed. In Perl, it is
far to much unnecessary overhead to split a string on every character,
into a two dimensional array of strings, using the null delimiter, just
gain access to a specific byte of the array. Then, if you modify the
array, you must re-join the data back into a single string. All that,
as opposed to just being able to say "$array[$i] = 'x'".
This is about the only complaint I can think of I have ever really had
with Perl.
--
Vincent Stemen
Avoid the VeriSign/Network Solutions domain registration trap!
http://www.InetAddresses.net
next prev parent reply other threads:[~2004-03-14 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 3:29 named directory expansion on strings Thorsten Kampe
2004-03-13 6:41 ` Bart Schaefer
2004-03-13 17:48 ` Thorsten Kampe
2004-03-14 18:54 ` Bart Schaefer
2004-03-14 21:24 ` Thorsten Kampe
2004-03-14 21:57 ` Vincent Stemen [this message]
2004-03-15 4:00 ` Python/zsh/perl [was: named directory expansion on strings] Jos Backus
2004-03-15 7:04 ` [OT]Python/zsh/perl " Bob Schmertz
2004-03-15 23:37 ` [OT]Python/zsh/perl Vincent Stemen
2004-03-17 4:03 ` [OT]Python/zsh/perl [was: named directory expansion on strings] Eric Mangold
2004-03-14 22:19 ` named directory expansion on strings Thorsten Kampe
2004-03-14 23:19 ` Bart Schaefer
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=20040314215700.GA61154@quark.hightek.org \
--to=zsh@hightek.org \
--cc=zsh-users@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).