Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!levels!xtdn From: xtdn@levels.sait.edu.au Newsgroups: comp.std.c Subject: Re: Frustrated trying to be portable Message-ID: <15938.27d2c9d3@levels.sait.edu.au> Date: 4 Mar 91 22:27:31 GMT References: <1991Feb20.175318.28496@zoo.toronto.edu> <2960@cirrusl.UUCP> <15367@smoke.brl.mil> Organization: University of South Australia Lines: 14 gwyn@smoke.brl.mil (Doug Gwyn) writes: > In article peter@ficc.ferranti.com (Peter da Silva) writes: > -The result of comparing two pointers into different objects is undefined > -but when you don't care about the result why worry? [...] > for some architectures the C run-time implementation > may trap on an attempt to compare two pointers to different objects. Does this include == and !=, or just the other inequalities? David Newall, who no longer works Phone: +61 8 344 2008 for SA Institute of Technology E-mail: xtdn@lux.sait.edu.au "Life is uncertain: Eat dessert first"