Re: bin/47795: ksh(1): unset(1)ting a readonly variable stops evaluation of startup script

[Steffen "Daode" Nurpmeso <sdaoden%gmail.com@localhost>]

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

From: Steffen "Daode" Nurpmeso <sdaoden%gmail.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/47795: ksh(1): unset(1)ting a readonly variable stops
 evaluation of startup script
Date: Mon, 06 May 2013 20:12:33 +0200

 Hello,
 
 matthew green <mrg%eterna.com.au@localhost> wrote:
  |The following reply was made to PR bin/47795; it has been noted by GNATS.
  |
  |From: matthew green <mrg%eterna.com.au@localhost>
  |To: gnats-bugs%NetBSD.org@localhost
  |Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
  |Subject: re: bin/47795: ksh(1): unset(1)ting a readonly variable stops \
  |evaluation of startup script
  |Date: Mon, 06 May 2013 23:45:19 +1000
  |
  | i think it is user-friendly for this not to fail with exit,
  | regardless of what POSIX says.
  |=20
  | if i break my .shrc, suddenly i can't login to fix it.
 
 =E2=80=A6 luckily you can :)
 But it's nonetheless a real bug (or, say -- ignorance of POSIX):
 
   $ ksh -i -c 'echo BEFORE; unset KSH_VERSION; echo AFTER'
 
  | .mrg.
 
 Ciao,
 
 --steffen