search for: _creates_

...ions (3.1) and implicitly cre- ated by the implementation (12.2). A declaration (clause 7) introduces names into a translation unit or redeclares names introduced by previous declarations. An object is a region of storage. An object is created by a definition (_basic.def_) Each declaration _creates_ an object. The word create means that each has a region of bytes, distinct from all others. > The changes to address Core issue 73 invalidates your reasoning No, they don't. I'm describing a fundamental feature of C and C++ that cannot be disputed. The most that can be done is t...

On Oct 15, 2008, at 3:53 PM, Mike Stump wrote: [...] > Objects are defined like so: > > Two pointers of > the same type compare equal if and only if they are both null, > both > point to the same object or function, or both point one past the > end > of the same array. > > This means they _must_ compare !=, if they are different objects. Aha! Thanks for

...rd "create" nor words to that effect, AFAICT. Furthermore, basic.life 3.8/7 makes it clear that an object may be created on top of another object, and the name of the first object will correctly evaluate to the new object. So that reasoning doesn't hold. > Each declaration _creates_ an object. The word create means that each > has a region of bytes, distinct from all others. No. >> The changes to address Core issue 73 invalidates your reasoning > > No, they don't. I'm describing a fundamental feature of C and C++ > that cannot be disputed. It s...

On Oct 15, 2008, at 8:28 AM, Chris Lattner wrote: > On Oct 15, 2008, at 6:58 AM, Tatu Vaajalahti wrote: >>> Yes, but why do you think they should get a different address? I >>> can >>> understand that it is surprising that they do, but determining >>> whether >>> this is legal or not requires reading the language standard. >>> Hopefully