🚀 go-pugleaf

In article <724520795.6224101@AppleLink.Apple.COM>,
GOTTSHALL.R@AppleLink.Apple.COM (Robert Gottshall,GEIS) wrote:
> 
> It really seems that the current approach to OOP isn't delivering its
> promises. Eiffel and Smalltalk do better, but they have different
> programming environments. Neither of the speakers mentioned any

Bedrock was not intended to address the programming environment issue. 
There is a lot of work going on in terms of C++ progamming environments in
the Unix market (from ParcPlace, HP, Sun, Lucid, etc.) and there's
Component Workshop in the Mac market.  

My understanding is that Bedrock was designed to work with any C++
compiler, and so it could be used in any of these environments.  (Assuming
CW does enough of C++, which I'm not clear about.)

> Apple said that Bedrock sort of tried to fit into the chasm between
> Hypercard and C, but I'm not convinced :) My vision of this project is

I wouldn't be convinced either.  HyperCard and C are totally different
things.  Even if he meant HyperTalk and C, those are languages and Bedrock
in a framework.

> events, etc.). Well, that was what TCL and MacApp were supposed to be.

The difference is that Bedrock was designed to be cross-platform, while TCL
and MacApp were not.

> Framework around as luggage. It seems to me that there should be a
> default application framework that is always active and is part of the
> system software. Your application essentially registers itself to the

That's a good point, but I think it's a third orthogonal point.  In theory,
there's no reason why Bedrock (or MacApp for that matter) couldn't be
shared among apps.

> environment. For example, why do we need to have "includes" or "USES"
> clauses in an OOP environment? There should be a big object database

This is where the C++ environments I mentioned are heading.  Certainly
Component Workshop does something like this, and I think the others may do
this as well.  But I don't think it's a framework issue, although when you
consider the entire task of creating an application you need all these
pieces (development environment, frameworks, shared libraries).

Larry Rosenstein
Taligent, Inc.

lsr@taligent.com