Re: ANSI-strict pointer aliasing rules - Mailing list pgsql-hackers

From Taral
Subject Re: ANSI-strict pointer aliasing rules
Date
Msg-id fa0147d90604271010n3dca44f1t88a05fa39ec274f@mail.gmail.com
Whole thread Raw
In response to Re: ANSI-strict pointer aliasing rules  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ANSI-strict pointer aliasing rules  (Taral <taralx@gmail.com>)
List pgsql-hackers
On 4/27/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Greg Stark <gsstark@mit.edu> writes:
> > There are other ways of achieving the same thing. Structs containing a union
> > for the subclass fields for example.
>
> Doesn't achieve the same thing, unless you mandate that every part of
> the system use the identical massively-overloaded union struct to refer
> to every node.

If we do subclassing like this:

struct Node { ... };
struct Value { struct Node; ... };
etc.

do we still run into the alias problem?

--
Taral <taralx@gmail.com>
"You can't prove anything."   -- Gödel's Incompetence Theorem


pgsql-hackers by date:

Previous
From: Taral
Date:
Subject: Re: ANSI-strict pointer aliasing rules
Next
From: Teodor Sigaev
Date:
Subject: Re: GIN - Generalized Inverted iNdex. Try 3.