Hi,
I've got a complain from one user, that builtin 'set' prints variables
that ksh does not recognize. He says it should print only those
variables, that can be used by ksh.
For example (start in bash):
a() { echo test; }
export -f a
ksh
set | grep BASH_FUNC
BASH_FUNC_a()=.....
unset 'BASH_FUNC_a()'
ksh: unset: BASH_FUNC_a(): invalid variable name
Maybe it should be omitted from 'set'. Per quick look - the
init.c:env_init should skip the variable not only when '=' is not found,
but also when variable name is invalid?
What do you think? I don't have strong opinion about this.
Michal
_______________________________________________
ast-users mailing list
ast-users@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-users
