Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!dogie.macc.wisc.edu!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: calculate member byte offset
Message-ID: <6590288@hplsla.HP.COM>
Date: 9 Oct 89 17:41:57 GMT
References: <1989Oct5.193826.24178@polyslo.CalPoly.EDU>
Organization: HP Lake Stevens, WA
Lines: 8

>This should be possible on ANY machine. You aren't actually dereferencing
>anything, you're just selecting a member function and passsing "this" to
>it. "alloc" had better be ready to get a NULL "this" though.

Well, my 680x0 compiler does a "lea" "load effective address" based on
what you pass "alloc" --which is not quite actually dereferencing the pointer.
But I wonder if machines that trap on null pointers wouldn't actually trap
on their equivalent to "lea" ???