🚀 go-pugleaf

<	the object model), but it has severe ovehead for object access. As we 
<	know, the 432 suffers from the slow performance problems which is a 
<	direct consequence of this "safest" object model. As a matter of fact, 
<	every object based systems has this kind of problems. So, what should 
<	be our choice ? a conventional architecture whose performance is
<	acceptable but sometimes has protection problems, or a object based 
<	system which has less protection problems but an (unacceptable ?) poor 
<	performance ?

Just because everyone in the past who has built object based systems has
produced a slow system is no reason to assume that all object based
systems must be this way.  Try posting your questions to comp.arch.
There are people working on fast object oriented machines who read
that group ( Hi Fritz! ).
-- 
Tim Smith			"Froh wie seine Sonnen fliegen
sdcrdcf!ism780c!tim		 Durch des Himmels praecht'gen Plan,
				 Laufet, Brueder, eure Bahn,
				 Freudig wie ein Held zum Siegen"