home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!harlqn!andrewa
- From: andrewa@harlqn.co.uk (Andrew Armstrong)
- Newsgroups: comp.sys.acorn.tech
- Subject: Re: How *does* one write a good text editor?
- Message-ID: <ANDREWA.92Sep10175732@gollum.harlqn.co.uk>
- Date: 10 Sep 92 17:57:31 GMT
- References: <17993@acorn.co.uk>
- Sender: news@harlqn.co.uk (Usenet News Account)
- Organization: Harlequin Limited, Cambridge, England
- Lines: 14
- In-Reply-To: pcolmer@acorn.co.uk's message of 24 Aug 92 07:07:02 GMT
-
-
- I've written a couple of editors that do this sort of thing, and I've
- always stored the text as a doubly linked list of lines, where each
- line is a structure containing the text for that line, color/font
- information, class information (what type of line - e.g. comment,
- function header), etc. This is very flexible, and makes the code very
- simple, but at least doubles the memory usage for an average file (for
- my most ambitious editor, I was quadrupling the memory usage!)
-
- I hope that's of some help - if you want to chat about it, feel free
- to e-mail me.
-
-
- Andy
-