beard@ux1.lbl.gov (Patrick C Beard) (08/31/89)
Michael, thanks for multiple segment code resources! I was developing in MPW C when I ran up against the 32k relative jump limit and decided to take the plunge and move my code to THINK C rather than segment it myself. Guess what, it works! There were some difficulties, of course, but mostly they've been solved. Some comments about the build process are in order, however. For those of us who right INITs, and trap patch code, here are a few suggestions that might make life a little easier. How about the ability to save where the code resource is built each time so that I can avoid the standard file dialog each time I want to try out a change in the code. How about the ability to control the resource type, id, and attributes of the code segments beyond the first segment? I would just like to be able to choose at least whether the segment is purgeable and to be loaded in the system heap. How about auto-loading, locking, and detaching all code segments in a multi-code segment project that has to stay resident. I think the current system is workable, but there could be many improvements. Let's hope some of them are made in the not-so-distant future. Thanks again, you've made my life a lot easier. ------------------------------------------------------------------------------- - Patrick Beard, Macintosh Programmer (beard@lbl.gov) - - Berkeley Systems, Inc. ".......<dead air>.......Good day!" - Paul Harvey - -------------------------------------------------------------------------------