Even if we were to have a "constant" twigil, I dont much like "$?" for it. No mnemomic value. For the builtins, it's not the constancy but the fact that they let you quey the config...
The case distinction wyou suggest orks just as well on the user side. Make your constants capitalized and your variables lowercase and no twigil is needed. This is a common convention across many langs anyway. On 3/14/08, herbert breunung <[EMAIL PROTECTED]> wrote: > > >> currently just used for compile time constants like $?LINE allright so > >> far so good. > >> but why not use that for all constants like > >> > >> my $?constant = 5; > >> > >> so it's compiletime (even late compiletime like in eval blocks) fix > >> binding to a value. > >> > > > > Because that variable comes from a different place than the $? constants. > > > thatswhy they are written uppercase. > You know $*IN is also internal var bat e.g. $*my is user defined. So i > see there no difference > if i define a $?var. > > herbert > -- Mark J. Reed <[EMAIL PROTECTED]>
