>Do you really mean to suggest that $SPECIALVARS be (by convention) >uppercase but built in types be (by grammar) lowercase? Absolutely. That's how it's already worked. The pragmata are lowercase module names are reserved to the Core. The type name is the class name, which is the package name, which is the module name, which is the pragma name. Larry's already pre-documented int, num, and str, IIRC. Predictable naming conventions are critical to knowing what is and what is not reserved. We actually have these conventions for modules, variables, and functions already. They're written down, although maybe not all in one place. --tom
- Re: RFC 171 (v1) my Dog $spot sh... Michael Fowler
- Re: RFC 171 (v1) my Dog $spo... Michael Fowler
- Re: RFC 171 (v1) my Dog $spot should ... Damian Conway
- Re: RFC 171 (v1) my Dog $spot sh... Piers Cawley
- RE: RFC 171 (v1) my Dog $spot should call a constructo... Evan Howarth
- Re: RFC 171 (v1) my Dog $spot should call a constructo... Michael G Schwern
- Re: RFC 171 (v1) my Dog $spot should call a const... James Mastros
- Re: RFC 171 (v1) my Dog $spot should call a c... Jonathan Scott Duff
- Re: RFC 171 (v1) my Dog $spot should call... Tom Christiansen
- Re: RFC 171 (v1) my Dog $spot should ... Buddha Buck
- Re: RFC 171 (v1) my Dog $spot sh... Tom Christiansen
- Re: RFC 171 (v1) my Dog $spot sh... Bart Lateur
- Re: RFC 171 (v1) my Dog $spot should ... Jonathan Scott Duff