NetBSD-Bugs archive

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

Re: standards/42828: Almquist shell always evaluates the contents of ${ENV} even if non-interactive



The following reply was made to PR standards/42828; it has been noted by GNATS.

From: Richard Hansen <rhansen%bbn.com@localhost>
To: "Greg A. Woods" <woods%planix.ca@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, standards-manager%netbsd.org@localhost
Subject: Re: standards/42828: Almquist shell always evaluates the contents
 of ${ENV} even if non-interactive
Date: Wed, 03 Mar 2010 15:39:54 -0500

 Greg A. Woods wrote:
 > With arrays both possibilities are easily and compatibly (to KSH at 
 > least, and perhaps Bash too) maintained without any necessary sacrifice 
 > to efficiency.
 
 I'm not sure I understand...  Are you suggesting that ${ENV[0]} (or the 
 equivalent ${ENV}) be used for interactive shells and ${ENV[1]} be used 
 for non-interactive shells?
 
 If so, I like it.  It's POSIX compliant and it allows us to maintain 
 NetBSD's functionality (but not backward compatibility) without having 
 to come up with a new environment variable that could collide with 
 someone else.
 
 Plus it would mean arrays.  :)  Lack of arrays is my biggest gripe with 
 the POSIX shell spec ("set -e" ambiguity is a close second).  However, 
 adding array support would be a *huge* change.  It'd be a challenge to 
 get community buy-in.
 
 -Richard
 


Home | Main Index | Thread Index | Old Index