Peter Scott <[EMAIL PROTECTED]> writes: | I've been reading "is" as a declarative imperative, something which | declares a property of something you are creating. Here it's being | used to modify the properties of something that already exists, and | it reads funny to me. Many properties that one can set at | declaration time are compile time only, yet this usage might suggest | to many people that they can be changed at run time. If you see | what I mean. Clearly we need 'becomes' and 'gets' for mutable properties, in addition to 'is' and 'has' for constant ones. -- http://www.dfan.org
- Exegesis2 and the "is" keyword Nathan Wiger
- Re: Exegesis2 and the "is" keyword Dave Storrs
- Re: Exegesis2 and the "is" keyword Michael G Schwern
- Re: Exegesis2 and the "is" keyword Nathan Wiger
- Re: Exegesis2 and the "is" keyword Carl Johan Berglund
- Re: Exegesis2 and the "is" keyword Peter Scott
- Re: Exegesis2 and the "is" keyword Dan Schmidt
- Re: Exegesis2 and the "is" keyword Austin Hastings
- Re: Exegesis2 and the "is" keyword Buddha Buck
- Re: Exegesis2 and the "is" keyword Daniel S. Wilkerson
- Re: Exegesis2 and the "is" keyword Simon Cozens
- Re: Exegesis2 and the "is" keyword Dan Sugalski
- Re: Exegesis2 and the "is" keyword John Porter
- Re: Exegesis2 and the "is" keyword Larry Wall