home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!spool.mu.edu!cass.ma02.bull.com!mips2!bull.bull.fr!julienas!loria!loria.fr!eker
- From: eker@loria.fr (Steven Eker)
- Newsgroups: comp.std.c++
- Subject: Re: Pointer comparisons
- Message-ID: <713@muller.loria.fr>
- Date: 29 Dec 92 15:38:04 GMT
- References: <1992Dec19.001851.22116@microsoft.com> <1992Dec23.182456.17185@lucid.com> <1992Dec24.200201.25709@microsoft.com> <1992Dec28.175218.15539@microsoft.com> <1992Dec29.042828.27808@lucid.com>
- Sender: news@news.loria.fr
- Organization: CRIN (CNRS) Nancy - INRIA Lorraine
- Lines: 17
-
- In article <1992Dec29.042828.27808@lucid.com>, jss@lucid.com (Jerry Schwarz) writes:
- [stuff deleted]
- |>
- |> So there really several related questions about this example.
- |>
- |> A: Does the ARM currently require a1!=a2? Apparently
- |> not, but I may have overlooked something.
- |>
-
- Has anyone noticed that slist_base::get() on p266 C++PL (2ed) assumes that
- pointers to different heap allocated objects compare unequal?
- Might this fail on a 486?
-
- There doesn't seem to be an easy fix for this example without maintaining
- a separate tail pointer.
-
- Steven
-