🚀 go-pugleaf

In article <1993Jan4.184530.11042@vax.oxford.ac.uk>,
vollrath@vax.oxford.ac.uk (Alun ap Rhisiart) wrote:
> 
> at it. My first reaction is that the demo is a little slow (certainly for
> what I expect of a C program), and not entirely stable.  I am well aware
> that something always goes wrong when you give someone a demo, so I'll
> spend some time on the files first.

That was my impression as well.  The program took longer to startup than I
expected.  Also, it crashed when I tried to stress it by saving to a full
volume or locked file.  

I also noticed that my PowerBook speaker clicks on startup, which I traced
to a call to _KillIO on the sound driver.  I don't know if this is in their
framework, but I don't see a reason for it.  (It's also a compatibility
risk because the sound driver isn't really supported.)

The startup time might not be a problem, but since the file saving code is
part of their framework, I would expect that problem to appear in every app
built with the same framework.  But the package does come with source code
so you can always fix the problem yourself.

Another point is that while OOPC works with a straight C compiler, it
really implements its own language.  There's a certain way you define
classes and methods, that you have to learn.  (It feels similar that what I
read in the Dylan manual, which should be closely related to the Lisp-based
object systems.)  Their "language" supports more dynamic features than C++,
which gives you a lot of power at the price of giving up some of the
compile-time checking.

The documentation file that comes with the demo includes reprints of 3
articles from Frameworks magazine (published by MADA), which include a
review of OOPC, and discussions of memory management and object systems in
general.


Larry Rosenstein
Taligent, Inc.

lsr@taligent.com