David, I think adding modifiers to typeset -n is an over kill and is not likely work as expected for variables which are not plain strings, e.g. integer, float, compound and typed variables. As Herbert said the same can be accomplished with 2 lines of code so I like to keep typeset -n as it is in the current ksh93t right now.
Olga On Wed, Aug 3, 2011 at 6:42 PM, David Korn <[email protected]> wrote: > cc: [email protected] > Subject: Re: Re: [ast-developers] typeset -u -n no longer works > -------- > > >> What is your position on this change in behavior? >> >> 1. The ksh-93s behavior is a bug, and it is fixed in the latest versions, >> >> or >> >> 2. the old behavior is the desired behavior, and the new versions have a >> bug. >> >> Thanks, >> Herbert. >> >> > > It is neither 1 or 2. It was an unintended feature. I tightened the checks > on options to typeset to prevent some combinations that made no sense and > could even lead to exceptions. I wasn't aware that typeset -nu and typeset > -nl > made sense at all. What it does is to first convert the value to upper or > lower case, and then create the reference. > > I could allow u and l as -n modifiers and document the behavior. > Let me know your opinions. > > David Korn > [email protected] > _______________________________________________ > ast-developers mailing list > [email protected] > https://mailman.research.att.com/mailman/listinfo/ast-developers > -- , _ _ , { \/`o;====- Olga Kryzhanovska -====;o`\/ } .----'-/`-/ [email protected] \-`\-'----. `'-..-| / http://twitter.com/fleyta \ |-..-'` /\/\ Solaris/BSD//C/C++ programmer /\/\ `--` `--` _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
