On 26 August 2013 20:53, David Korn <[email protected]> wrote: > cc: [email protected] [email protected] > Subject: Re: Re: [ast-developers] [uwin-developers] Next alpha/beta and > roadmap for ksh93v? > -------- > >> On 26 August 2013 16:30, David Korn <[email protected]> wrote: >> > cc: [email protected] >> > Subject: Re: Re: [ast-developers] [uwin-developers] Next alpha/beta and >> > roadma >> p for ksh93v? >> > -------- >> What you loose is flexibility. The flexibility of user-defined >> constants or even typed functions. I've experimented with Mr. Mainz's >> patch a bit and found it useful to add functions to floats: >> ksh -c 'compound .sh.mathconst=( float LDBL_MYVAL=nan ) ; function >> .sh.mathconst.LDBL_MYVAL.getn { .sh.value=4 ; } ; float x=5.5 ; print >> $((x.MYVAL)) ${x.MYVAL}' >> 4 4 > To me, this is a reason against it. I don't want constants that are not > constant and differ by type.
No no, you got it wrong. I wished to demonstrate that it is possible (later!?) to implement per-type functions, e.g. typeset -E x; (( c=x.hashCode() )) which calls a function hashCode which is specific for this type. Like JAVA does in http://docs.oracle.com/javase/6/docs/api/java/lang/Double.html#hashCode%28%29 Wendy _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
