Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!emory!mephisto!prism!sun13!gw.scri.fsu.edu!pepke
From: pepke@gw.scri.fsu.edu (Eric Pepke)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Speaking of Munger...
Message-ID: <256@sun13.scri.fsu.edu>
Date: 13 Jul 90 21:16:00 GMT
Sender: news@sun13.scri.fsu.edu
Organization: Florida State University, but I don't speak for them
Lines: 20
References:<233@sun13.scri.fsu.edu> <42917@apple.Apple.COM> <1990Jul13.142801.6843@eng.umd.edu>

In article <1990Jul13.142801.6843@eng.umd.edu> russotto@eng.umd.edu 
(Matthew T. Russotto) writes:
> The real reason your MemError() test is failing is that printf uses the 
memory
> manager, and that clears MemErr (because the calls printf makes succeed)

No.  C evaluates the operands to printf before it invokes it.

However, you are partially correct in that it was my error.  It's not the 
printf call that resets MemErr; it's the GetHandleSize.  If I put the 
return value of MemError into a variable before calling that, it returns 
-108, which is exactly what I had hoped.

Eric Pepke                                    INTERNET: pepke@gw.scri.fsu.edu
Supercomputer Computations Research Institute MFENET:   pepke@fsu
Florida State University                      SPAN:     scri::pepke
Tallahassee, FL 32306-4052                    BITNET:   pepke@fsu

Disclaimer: My employers seldom even LISTEN to my opinions.
Meta-disclaimer: Any society that needs disclaimers has too many lawyers.