zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Field splitting with trailing non-whitespace IFS characters (fwd)
Date: Mon, 7 Mar 2005 12:49:29 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0503071248380.7630@toltec.zanshin.com> (raw)

Anybody want to (or want me to) say anything more about this to the
austin-group list?


---------- Forwarded message ----------
Date: Mon, 7 Mar 2005 09:50:52 +0000
From: Geoff Clare <gwc@opengroup.org>
To: austin-group-l@opengroup.org
Subject: Re: Field splitting with trailing non-whitespace IFS characters
Resent-Date: 7 Mar 2005 09:51:17 -0000
Resent-From: austin-group-l@opengroup.org
Resent-To: austin-group-l@opengroup.org

Assuming there is consensus that Glenn's test script reflects the
intended POSIX requirements, I propose the following changes to
XCU6 to clarify the standard and to correct the defect identified
on the read page.

In 2.5.3 Shell Variables:

Delete "(Input Field Separators.) " from the beginning of the IFS
description.

On the sh page under ENVIRONMENT VARIABLES:

Delete "(Input Field Separators.) " from the beginning of the IFS
description.

Add to RATIONALE on the sh page:

"The name IFS was originally an abbreviation of Input Field Separators,
however this name is misleading as the IFS characters are actually
used as field terminators."

In 2.6.5 Field Splitting, paragraph 2:

Change "The shell shall treat each character of the IFS as a delimiter
and use the delimiters to split the results of parameter expansion and
command substitution into fields."

to "The shell shall treat each character of the IFS as a delimiter
and use the delimiters as field terminators to split the results of
parameter expansion and command substitution into fields."

On the read page:

Change "If there are fewer var operands specified than there are
fields, the leftover fields and their intervening separators shall be
assigned to the last var."

to "If there are fewer var operands specified than there are fields,
the last var shall be set to a value comprising the following elements:

    * the field that corresponds to the last var in the normal
      assignment sequence described above,
    * the delimiter(s) that follow the field corresponding to the
      last var, and
    * the remaining fields and their delimiters."


Any comments before I submit these as an aardvark?

-- 
Geoff Clare <g.clare@opengroup.org>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England


                 reply	other threads:[~2005-03-07 20:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.61.0503071248380.7630@toltec.zanshin.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).