🚀 go-pugleaf

In article <keSKjBC00iQQ0AHUcK@andrew.cmu.edu>, gh1h+@andrew.cmu.edu (Gary Hooyman) writes:

|> I recently faced the same problem, and at first my solution was to
|> maintain protability and implement my own metainfo class.  This class
|> had attributes that managed class name, slot names, etc and had methods
|> for redefining a class given a prototype instance using eval and quotes
|> that did not require any calls to metaobject protocol methods.

My colleague, Len Charest, had the same suggestion. We didn't like it.

|> 
|> I have since reimplemented this  to use MOP methods because:
|> 
|> 	Much of it is available in Lucid 4.02 (on DEC)
|> 	Implementation became cleaner because clos was managing
|>                    the metainformation so I didn't have to - my code was not
|>                     robust or general enough to do the job very well
|>               MOP seems to be becomming standardized 
|>                      (this I say only as an outsider looking in - it may or may
|>                         not be true, but it is my observation)

I agree that's the way to go.

|> 
|> 
|> If you want to see any code examples, I can send them, but I

If possible, please send or post examples and the mop solution.

-- 
Nicolas Rouquette
Artificial Intelligence Group
Jet Propulsion Laboratory
California Institute of Technology
4800 Oak Grove Drive
M/S 525-3660
Pasadena, CA 91109

phone: (818) 306-6171
fax:   (818) 306-6912
Email: rouquett@aig.jpl.nasa.gov