>From: Gordon Vreugdenhil <gordonv@model.com> >The point is that "this" is NOT a structure or element reference -- it >is the context of the method. I have always regarded "this" as a special identifier that represents a class object passed to a non-static method as a hidden argument. From that viewpoint, "this.member" is just a class member reference. And from that viewpoint, if the randomize constraint is viewed as being resolved in a non-static method of the class object, then there will always be a "this" to resolve it to in the class object. I admit that my viewpoint is that of a compiler implementor, as I have never embraced the "object oriented" mindset. However, it does seem to be a self-consistent viewpoint. Are there any other situations in the language that demonstrate that "this" is not just a special class handle variable? Are there any situations aside from in-line constraints where a name can be resolved in two different class scopes, to provide precedent for how this should behave? I assume not. Steven Sharp sharp@cadence.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Sat Dec 15 04:47:10 2007
This archive was generated by hypermail 2.1.8 : Sat Dec 15 2007 - 04:47:36 PST