From: Paul Haahr <firstname.lastname@example.org>
To: Tim Goodwin <email@example.com>
Subject: Re: rc 1.6 $version
Date: Wed, 3 Apr 2002 10:06:47 -0500 [thread overview]
Message-ID: <cZGNG75Vn2@dmul.paulhaahr.com> (raw)
> > I'd prefer $rc-version, but either should be fine.
> (As it turns out, this is all irrelevant, but I have would two
> objections to this. First, `-' turns on free careting, [...]
Yeah, I forgot about that. (We had fixed that in es.)
> Secondly, rc is meant to be C-ish, not Lisp-ish.)
That, too, we fixed in es.
> Mea culpa. I failed to realise that there are two types of special
> variable in rc: 1) those that merely have a default initial value, and
> 2) those that invoke special code when substituted. Till now,
> $version was in category 2. I've just moved it to category 1.
This seems quite sensible.
> As a separate matter, several variables are not exportable. These
> are: $apid, $apids, $cdpath, $home, $ifs, $path, $pid, and $*.
> (Remember that $cdpath, $home, and $path are all aliased to upper case
> versions, which *are* exportable. Also, the default assignment to
> $path happens before $PATH is examined: so if $PATH is set, $path will
> acquire its value instead of the default.)
> I think $bqstatus and $status ought to be non-exportable too. I've
> just made them so; you can all see what this breaks in the next
> release candidate :-).
Seems good to me.
- Is $version exportable?
- Is $version exported if the user doesn't assign to it?
- Is $version inherited from the environment?
next prev parent reply other threads:[~2002-04-03 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 22:37 erik quanstrom
2002-03-27 13:27 ` Tim Goodwin
2002-03-27 21:12 ` Carlo Strozzi
2002-03-30 18:43 ` Paul Haahr
2002-03-31 15:13 ` Carlo Strozzi
2002-04-03 14:31 ` Tim Goodwin
2002-04-03 15:06 ` Paul Haahr [this message]
2002-04-04 10:04 ` Tim Goodwin
2002-04-04 21:42 ` Scott Schwartz
2002-04-04 21:54 Byron Rakitzis
2002-04-05 8:35 ` Tim Goodwin
2002-04-05 1:38 Smarasderagd
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
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).