bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: POSIX compliance of shells - where to ask/talk about it?


From: Andreas Schwab
Subject: Re: POSIX compliance of shells - where to ask/talk about it?
Date: Fri, 26 Jul 2002 20:12:59 +0200
User-agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.3.50 (ia64-suse-linux)

address@hidden (Ian Lynagh) writes:

|> Hi all,
|> 
|> Where should one ask/talk about POSIX shell compliance (looking for a
|> mailing list probably)?
|> 
|> I am reading the standard at
|> http://www.opengroup.org/onlinepubs/007904975/utilities/xcu_chap02.html
|> and finding it very imprecise - disappointingly so (am I looking in the
|> wrong place?). I am therefore looking to implementations to clarify the
|> standard, but with things like this (all shells invoked as sh, bash
|> given --posix):
|> 
|> printf "%s\n" `echo '\\\\\\\\\\\\\\\\'`
|> printf "%s\n" "`echo '\\\\\\\\\\\\\\\\'`"
|> 
|> Using shells/ash:
|> \\\\
|> \\\\
|> 
|> Using shells/bash:
|> \\\\\\\\
|> \\\\\\\\
|> 
|> Using shells/zsh:
|> \\\\
|> \\\\\\\\

I think the key difference here is whether echo is interpreting
backslashes or not.  By default, bash's builtin echo does not interpret
backslashes, and if you use "echo -e" you get the same output as ash.  zsh
seems to be the odd case again.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 N체rnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



reply via email to

[Prev in Thread] Current Thread [Next in Thread]