Garrett D'Amore writes: > Have the upstream providers given thought to dealing with changes like > this and their impact on already-deployed scripts? (Maybe there aren't > any that we care about yet, since our ksh93 is still so new.)
We've already had such problems. See CR 6667990 for one such accident; you can't call your local function "start" and upgrade safely from Sun's old ksh88 to ksh93. > I'm concerned, going forward, as ksh93 syntax becomes more prevalent, > that bringing in changes like the above may have unintended consequences > in scripts or even ON delivered components, which we cannot easily find > or test. This probably isn't a good place to design a solution, but I share the sense of unease. It puts script writers on shaky ground if they can't either specify a known environment or predict what's "safe." -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
