From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-workers@math.gatech.edu
Subject: intepreting octal and globbing breakage
Date: Mon, 22 May 1995 12:51:06 -0400 [thread overview]
Message-ID: <9505221651.AA23094@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Sat, 20 May 1995 11:55:01 MDT." <9505201755.AA25392@bjerknes>
> RC> I've made a test release zsh-2.6-beta9-test2.tar.gz
> RC> and put it in the testing directory of the archive.
> RC> I've been sorta busy this week so I haven't finished
> RC> a lot of the things I want to do before I release the
> RC> next beta. So I want to work on it for another week
> RC> or so before I make a real beta release.
>
> Are you going to address the zstrtol/strtol lossage in this beta?
> It's responsible for breaking brace and numeric range globbing:
> In this case, can't we just go back to using zstrtol like in the old days?
> At least it works.
That's one of the reasons I just made a test release rather than the
real thing. I'll probably have to go back using zstrtol. That would
also make it easy to fix it so that numbers beginning with '0' are not
interpreted as octal. I sorta hate to do this, since then zstrtol
would be even more incompatible with the standard strtol. I also hate
the idea of interpreting 0xff has hex, but not interpreting 010 as
octal. I also hate the idea of adding (yet another) option to control
this.
What does ksh and bash do? I'm inclined to go with the principle of
least surprise and make this compatible with however the other shells
handle this.
At any rate, I'll try to fix the globbing breakage before I release
beta9.
rc
zsh@math.gatech.edu
next prev parent reply other threads:[~1995-05-22 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-05-19 9:35 test release Richard Coleman
1995-05-20 17:55 ` Mark Borges
1995-05-22 16:51 ` Richard Coleman [this message]
1995-05-22 18:39 ` intepreting octal and globbing breakage Zoltan Hidvegi
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=9505221651.AA23094@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=zsh-workers@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).