On Mon, Jun 27, 2011 at 2:44 PM, Christopher Zimmermann <madro...@zakweb.de> wrote: > Ok, I got it. But wtf? Thats creepy! Is there any rationale behind this > strange bourne behaviour?!?
I would guess historical accident or some quirk of the implementation. Then once it was discovered, it became unfixable because of back compat. Fortunately, ksh is not strictly tied to bourne compatibility.
