Skip site navigation (1) Skip section navigation (2)

Re: ANSI-strict pointer aliasing rules

From: Taral <taralx(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ANSI-strict pointer aliasing rules
Date: 2006-04-27 17:10:31
Message-ID: fa0147d90604271010n3dca44f1t88a05fa39ec274f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 4/27/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Greg Stark <gsstark(at)mit(dot)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(at)gmail(dot)com>
"You can't prove anything."
    -- Gödel's Incompetence Theorem

In response to

Responses

pgsql-hackers by date

Next:From: Teodor SigaevDate: 2006-04-27 17:10:35
Subject: Re: GIN - Generalized Inverted iNdex. Try 3.
Previous:From: TaralDate: 2006-04-27 17:04:45
Subject: Re: ANSI-strict pointer aliasing rules

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group