Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!dog.ee.lbl.gov!ux5.lbl.gov!beard
From: beard@ux5.lbl.gov (Patrick C Beard)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C++ used for DAs?????
Message-ID: <12618@dog.ee.lbl.gov>
Date: 29 Apr 91 22:58:56 GMT
References: <41728@cup.portal.com>
Reply-To: beard@ux5.lbl.gov (Patrick C Beard)
Distribution: usa
Organization: Berkeley Systems, Inc.
Lines: 24
X-Local-Date: Mon, 29 Apr 91 15:58:56 PDT

In article <41728@cup.portal.com> Christopher_C_Lapp@cup.portal.com writes:
#Can anyone give me advice on how to adapt the rigid rules of writing
#desk accessory software (the five procedure names must be named according
#to rules, etc.) to using C++ objects in the development?  Has anyone
#had any experience?
#Chris Lapp
#Lingua Science
#email: Christopher_C_Lapp@cup.portal.com



You should check out my article in the October issue of d e v e l o p about
polymorphic code resources in C++.  In it, I describe how to create
code resources that use virtual functions.  In preparing for the article
I created several examples of this technique:  an iconifiable window definition
function (object actually); a driver for interapplication communication, and
the Memory desk accessory (example included with MPW) rewritten to use a
driver object.  I can make all of these examples available to the net if
there is enough interest.

--
//  Patrick C. Beard, Software Engineer, Berkeley Systems, Inc.
//                    "Heroes of technology."
//   beard@lbl.gov, d0346@applelink.apple.com (ATTN: Patrick)