From: Carlo Strozzi <firstname.lastname@example.org> To: email@example.com Subject: Re: rc 1.6 $version Date: Wed, 27 Mar 2002 16:12:26 -0500 [thread overview] Message-ID: <20020327221226.A25153@strozzi.it> (raw) In-Reply-To: <firstname.lastname@example.org>; from email@example.com on Wed, Mar 27, 2002 at 08:27:16AM -0500 On Wed, Mar 27, 2002 at 08:27:16AM -0500, Tim Goodwin wrote: > > is there any way that $version could be changed either > > to not be so magic (i.e. assigned at startup time) or > > better something like _rc_version_. > > The `version' variable was introduced in rc-1.6b1 (replacing the `-V' > flag, which itself was new in rc-1.5b4). Thus, it's never been in a > full release. Thus, I'm prepared to change it :-). > > Any objections to `rc_version'? rc already has a few reserved variable names, like $pid, $bqstatus, $status, and so on. Others, like $version, could be added in the future. It would be nice to have a naming-convention for reserved names, so that one knows in advance what names should be left alone. The proposed `rc_version' is ok, and my suggestion is to set the `rc_' prefix aside for rc reserved variables. We would then have rc_path, rc_home, rc_whatever. Of course, for backward compatibility we will continue to have also $pid, $path and that, but from now on there whould at least be a standard for any new rc needs, and that could be documented in the man page. Since rc supports 'funny' characters in names, the reserved ones could even be 'rc.something', so that they are even more peculiar. Just my two-cent. bye, carlo -- For easier reading please set the Courier font. Messages larger than 30 KB may not receive immediate attention. Freedom for Business: http://swpat.ffii.org
next prev parent reply other threads:[~2002-03-27 23:08 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 [this message] 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 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
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=20020327221226.A25153@strozzi.it \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: rc 1.6 $version' \ /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
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).