Path: utzoo!censor!geac!jtsv16!uunet!wuarchive!gem.mps.ohio-state.edu!apple!apple.com!chewy
From: chewy@apple.com (Paul Snively)
Newsgroups: comp.lang.lisp
Subject: Re: LISP compiler? (really future of MACL)
Message-ID: <5130@internal.Apple.COM>
Date: 10 Nov 89 17:45:10 GMT
Organization: Apple Computer, Inc.
Lines: 84
References:<5057@internal.Apple.COM> <89Nov7.234038est.2758@neat.cs.toronto.edu> <5081@internal.Apple.COM> <21192@uflorida.cis.ufl.EDU>

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> I view MACL
> as the prototyping language for Mac applications.

Apple views MACL as an environment for developing shippable applications, 
not merely for prototyping them.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> As such I need a fast
> nice object system such as Apple CLOS, not PCL.

Of course we'll have our own CLOS, just not in 1.3. :-)

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> I need all the great
> examples that MACL has given out converted and consolidated to work
> with the new system.

By "new system," I presume you mean CLOS.  Of course we'll do that too.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> I just want high level objects that correspond
> to MAC interface parts.

We've already got that, and will keep it.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> In addition, I would like to see improved
> support for printing, and version7 stuff.

What exactly does this mean?  We will definitely support System 7.  What 
do you need relative to printing?

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> I think it is important that Apple keep MACL progressing in the
> direction of new features like CLOS and CLIM.  CLIM is important.
> Apple is in the interface/easy-to-use camp and CLIM is a UIMS, it seems
> like a natural fit.

We certainly agree about CLOS.  CLIM may or may not be offered as an 
option for the system.  It's not a priority for us, as we already have a 
user environment that we'd like to keep consistent, and which is, in our 
collective opinions, in many ways better than CLIM.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> The inspector doesnt allow editing yet

It does if it can find the source code.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> FRED hasnt changed

Actually, it has, but I need to know more about what you want from it.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> the manual needs revising

Done, as of 1.3.

In article <21192@uflorida.cis.ufl.EDU> mfi@serc.cis.ufl.edu (Mark 
Interrante) writes:
> the interface generator
> tool is embarassing in comparison to the NeXT.

Also vastly improved as of 1.3.

MACL 1.3 should be at APDA within the next two weeks or so (I just got the 
frozen code a few days ago).

__________________________________________________________________________
Just because I work for Apple Computer, Inc. doesn't mean that they 
believe what I believe or vice-versa.
__________________________________________________________________________
C++ -- The language in which only friends can access your private members.
__________________________________________________________________________