Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!husc6!ut-sally!brian
From: brian@ut-sally.UUCP (Brian H. Powell)
Newsgroups: comp.sys.mac
Subject: TextEdit error checking
Message-ID: <8654@ut-sally.UUCP>
Date: Mon, 3-Aug-87 17:43:22 EDT
Article-I.D.: ut-sally.8654
Posted: Mon Aug  3 17:43:22 1987
Date-Received: Tue, 4-Aug-87 05:36:27 EDT
Organization: U. Texas CS Dept., Austin, Texas
Lines: 30
Keywords: Running Out of Memory


     Okay, next question.  How do you figure out if TextEdit had problems
carrying out some operation?

     I've been pushing my program to the limit to try to iron out what happens
when it gets low on memory.  When I do a TEPaste, for instance, with memory
very full, I usually get garbage displayed in addition to the text that it's
pasting.  MemError doesn't say anything, and of course the TE procedures don't
return any error code.  (In case you're wondering, I'm pasting just under 32K
bytes into an empty edit window.)

     How's the best way to handle this?  Should I leave a large chunk of
memory free so that nothing should ever fail for lack of memory?  Is there
something I can check in the TE record that might help me figure out if
something went wrong?  (e.g., comparing the teLength after a paste to make
sure the size actually increased by the proper value...  Can I really depend
on this?)

     Thanks for any help.

Brian H. Powell
		UUCP:	{ihnp4,seismo,ctvax}!ut-sally!brian
		ARPA:	brian@sally.UTEXAS.EDU

   _Work_					 _Not Work_
  Department of Computer Sciences		P.O. Box 5899
  Taylor Hall 2.124				Austin, TX 78763-5899
  The University of Texas at Austin		(512) 346-0835
  Austin, TX 78712-1188
  (512) 471-9536