Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ucsd!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.arch Subject: Re: 64 bits--why stop there? Message-ID: Date: 30 Aug 90 13:26:56 GMT References: <6106@vanuata.cs.glasgow.ac.uk> <2437@crdos1.crd.ge.COM> <631@array.UUCP> <225@csinc.UUCP> <1372@svin02.info.win.tue.nl> <141569@sun.Eng.Sun.COM> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 17 In article <141569@sun.Eng.Sun.COM> lm@sun.UUCP (Larry McVoy) writes: > (1) Unix has reached the age where it has what can be called dusty deck code. > And this code frequently does stuff like > char *bar = (char*)malloc(100); > which doesn't work under Rob's machine. It won't work on *any* machine where sizeof(int) != sizeof(char*), or where pointers are returned differently than integers (as in some 68000 compilers that return ints in D0 and pointers in A0 for the very good reason that it's more efficient that way when the result is going to be used immediately), or on any number of other environments that don't look like VAXes. > Do we want to support this code? No. -- Peter da Silva. `-_-' +1 713 274 5180. 'U` peter@ferranti.com