Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!dartvax!eleazar.dartmouth.edu!earleh
From: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TranSkel, TransEdit help...
Keywords: TransSkel, TransEdit
Message-ID: <15491@dartvax.Dartmouth.EDU>
Date: 9 Sep 89 05:27:12 GMT
References: <6383@ingr.com>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: earleh@eleazar.dartmouth.edu (Earle R. Horton)
Organization: Thayer School of Engineering
Lines: 31

In article <6383@ingr.com> henges@ingr.com (John Hengesbach) writes:
>
>I am using Transkel, TransEdit, et al. and I have a couple of questions.
>
>1)  Why is there a hard coded limit of 32K for a file to be editted?

TransEdit uses TextEdit for editing text.  TextEdit uses short integers
in places that guarantee a serious error if the text being edited is
more than 32k characters in length.  When the average amount of RAM in
a Mac was 128k, and when 32k was a HUGE chunk of memory, then you might
have scraped by using TextEdit as the base for a RAM-based text editor.
Now, however, things are different and TextEdit is only useful as a
support module for the Dialog Manager.

****************************************************************************
* In my opinion, those who attempt to use TextEdit as the base for a       *
* serious text editor perpetuate the myth that the Mac is a toy.  Out of   *
* eighteen Sample Code packages on apple.com, three are attempts at a text *
* editor using TextEdit.  Phhht!                                           *
****************************************************************************

There is no rule that says you cannot write your own text handling
package.  Many people have done so.

>2)  On the same thread of thought, once memory is allocated for the
>    file in a text window, when/how does it get freed up again?

Wrfhf Shpxva Puevfg, lookit the code, willya?  It's in Clobber() in
TransEdit.c.

Earle R. Horton