Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!mips!apple!well!oster From: oster@well.sf.ca.us (David Phillip Oster) Newsgroups: comp.sys.mac.programmer Subject: Re: Detecting Color Depth Message-ID: <21635@well.sf.ca.us> Date: 13 Nov 90 10:23:06 GMT References: <1990Nov6.231358.18153@Neon.Stanford.EDU> <8068@adobe.UUCP> Distribution: na Organization: Whole Earth 'Lectronic Link, Sausalito, CA Lines: 19 In article <8068@adobe.UUCP> hawley@adobe.UUCP (Steve Hawley) writes: _>In article phils@chaos.cs.brandeis.edu (Phil Shapiro) writes: _>>#define ScreenDepth(gdh) ((**((**gdh).gdPMap)).pixelSize) _>>#define MaxColors(gdh) (1L<>where gdh is a GDHandle (graphic device handle). _>Phil -- if your handle is not locked, isn't there a potential problem with _>the order of evaluation of the dereferences --especially in a context that _>may move memory? _>Steve Hawley Steve, you should go back and reread Inside Macintosh and Knaster again. There is NO WAY that a dereference of a pointer is going to move memory, and no way that a string of simple dereferences is ever going to cause a problem. -- -- David Phillip Oster - Note new signature. Old one has gone Bye Bye. -- oster@well.sf.ca.us = {backbone}!well!oster