home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.forth.mac
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!hpscit.sc.hp.com!cupnews0.cup.hp.com!news1.boi.hp.com!hp-pcd!hp-vcd!nuntius
- From: John Matthews <jm@vcd.hp.com>
- Subject: Writing INIT's with Yerk/MOPS
- Sender: news@vcd.hp.com (News user)
- Message-ID: <C0K85p.M9A@vcd.hp.com>
- X-Useragent: Nuntius v1.1a5
- Date: Sat, 9 Jan 1993 00:03:25 GMT
- Organization: Hewlett-Packard
- Lines: 19
-
- I am new to Mac-Forth programming (Although I did do some a long time ago
- on the Atari 800 system). I would be interested in using either Yerk or
- MOPS to do the following:
-
- 1) Write quick little utility Apps to give to my co-workers. I would like
- to be able to bring up windows, draw text and graphics into them, etc...
- (The usual Mac U.I. stuff). Minimizing development time is more important
- to me than minimizing memory usage or time efficiency. Good debugging
- capability is particularly important.
-
- 2) Write Stand-alone code resources, particularly INIT's. Often I want to
- patch some traps to keep track of some aspect of the O.S. I would like to
- be able to create an INIT that, whenever it was entered, would dump me
- into a Forth interpreter/debugger so I could incrementally add and test
- the INIT's functionality. Once I finished (after many reboots), I would
- like to create a small INIT that executes in the desired manner.
- (Actually, the Forth interpreter + windowing code is likely to be small
- enough that I wouldn't mind if it remained in the init, as long as users
- of the INIT don't see it).
-