[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: where does mcl fit in?

In article <697487315.4838601@AppleLink.Apple.COM> 
UK0392@AppleLink.Apple.COM (EHN & DIJ Oakley,BDV) writes:
> flexible and customisable.  The only temporary drawback is that until 
2.0 final
> ships, making smallish standalone apps is not possible (standalones are 
> 1.3
> meg in size), and I think that MCL will always be rather more voracious 
of RAM
> and processor grunt than simpler compiler systems.  You do not of course 

If a user has several MCL-based standalone apps, would it be possible to 
let these apps share a common block of code, to let parts of RTS be a 
separate process which could be shared by several other processes?
  The grandmother of CLOS, SIMULA, was often claimed to be too bulky to do 
serious programming with.  However, the very elegant DEC-10 implementation 
had several "shareable high-segments" for compiler and RTS, which were 
even shared by all users, which made single Simula programs themselves 
require reasonably little disk and memory space.
  Another parallell is the MacOS:  Several other GUI, for instance X on 
Decstations, require all graphics functions to be linked with each program.

Espen J. Vestre,                          espen@coli.uni-sb.de
Universitaet des Saarlandes,        
Computerlinguistik, Gebaeude 17.2 
Im Stadtwald,
D-6600 SAARBRUECKEN, Germany           tel. +49 (681) 302 4501