Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!mit-eddie!bloom-beacon!eru!hagbard!sunic!fuug!kth.se!cyklop.nada.kth.se!news
From: d88-jwa@dront.nada.kth.se (Jon W{tte)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp
Message-ID: <1991Jan8.171033.25112@nada.kth.se>
Date: 8 Jan 91 17:10:33 GMT
References: <1991Jan3.221839.21979@athena.cs.uga.edu> <Jan.4.13.24.17.1991.14211@athos.rutgers.edu> <14571@hoptoad.uucp> <11656@goofy.Apple.COM>
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 16

In article <11656@goofy.Apple.COM> lsr@Apple.com (Larry Rosenstein) writes:

>Agreed.  There would be no point in trying to adapt MacApp to allow writing
>other kinds of programs (DAs, INITs, etc.).  The structures of these 
>programs are totally different from that of an application.  It might be
>worthwhile to do a framework for writing DAs, but you would want to start
>from scratch.

Check out Think C - it provides a basic framework for writing
"object-oriented" cdevs, and possibly DAs to (haven't looked)

It sure allows OOP in code resources, anyway.

							H+

Jon W{tte, Stockholm, Sweden, h+@nada.kth.se