Well reflective facilities are part of it.  But you also have have to
worry about things like a squeaklet drawing crud on the screen, or a
squeaklet taking all keyboard input for itself.  Such things *aren't*
don't really have to do with reflection, but they still need to be
addressed.


Lex



Marcel Weiher <marcel at metaobject.com> wrote:
> Doesn't this essentially boil down to "declarative Smalltalk"?
> 
> So as a rough approximation, you would have:
> 
> 1.	Declarative Smalltalk without I/O for Applets
> 2.	Declarative Smalltalk for most programming tasks
> 3.	Fully reflective Smalltalk where declarative Smalltalk is lacking
> 
> which might even be a rough first approximation of the various  
> levels of meta-access described by Alan.  For developers, the fences  
> between the levels should be noticable but easily and comfortably  
> surmountable.  For applets, they need to be absolutely impenetrable,  
> but I think that they are essentially the same fences.
> 
> Marcel
> 
> > From: Peter Crowther <Peter.Crowther at IT-IQ.com>
> >
> > > From: Lex Spoon [mailto:lex at cc.gatech.edu]
> > > It's easy to make a modified compiler which removes booboos
> > > like this.
> > > Things to remove:
> > >
> > > 	1. <...> primitives
> > > 	2. thisContext
> > > 	3. access to the full Smalltalk dictionary
> >
> > Having done something this to nail down VisualWorks...
> >
> > 4. Ability to modify the Compiler.
> > 5. Ability to create your own Compiler.
> > 6. Ability to instantiate arbitrary classes and therefore create  
> your own
> > methods and fill 'em with bytecodes.
> > 7. Ability to become: on methods to swap 'em for others that  
> you've created
> > and are waiting in the wings.
> > 8. Debug primitives such as instVarAt:put: