Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: character sets for internal zsh tests
- X-seq: zsh-workers 21209
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: Re: PATCH: character sets for internal zsh tests
- Date: Thu, 28 Apr 2005 16:09:30 +0100
- In-reply-to: <1050428145443.ZM31609@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200504281141.j3SBfI4g019987@xxxxxxxxxxxxxx> <1050428145443.ZM31609@xxxxxxxxxxxxxxxxxxxxxxx>
Bart Schaefer wrote:
> Ooh, another idea: make them all-caps, e.g. [:WORD:].
That would be OK.
> Given the recent austin-group discussion about how "separators" is
> misused in "IFS" (they're really "internal field terminators") it may
> in fact be better to avoid "sep".
I'm going to end up with an essay like
[:FIELDSEPARATOREXCEPTTHEYSOMETIMESGETABITPRUNED:]
if I do that. Not just the variable name but also the documentation
consistently uses the word "separator". Introducing "terminator" now is
going to confuse the issue. Hasta la vista.
> However, unless you go with all-
> caps [:IFS:] I think you should pick something that looks like a word
> (in the English dictionary sense) or an abbreviation, rather than an
> acronym. Unfortunately I don't have any good suggestions just now.
[:FIELDSEP:] and [:WHITESEP:], perhaps?
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
Messages sorted by:
Reverse Date,
Date,
Thread,
Author