Has anyone observed class behavior whereby you can end up with more than
one class defined of the same name in the same package?  We had been
using some metaclasses which we initially blamed for the problm.  I
eliminated the metaclasses from our system in the hopes of eliminating
this error.  Unfortunately, that didn't work.  

Below you will see the results of running clos:class-direct-subclasses
on one of the classes in my heirarchy.  Notice that there are multiple
classes of the same name.  This wrecks havoc on the object system to say
the least.  We had attributed it to the meta object protocol which is
hazardous to use.  I really wish that I weren't seeing it now after I
removed all the meta classes.  

We are using Allegro 4.3 on SGIs with all the latest patches downloaded
from the Franz site.

USER(7): (clos::class-direct-subclasses (find-class
'activity::contingent-activity))
(#<STANDARD-CLASS ACTIVITY-SPACE::ND-AIR-MIDAS-DECIDE-ACTIVITY>
 #<STANDARD-CLASS ACTIVITY-SPACE::ND-AIR-MIDAS-DECIDE-ACTIVITY @
#x10864ada>
 #<STANDARD-CLASS MIDAS-INTERNAL:DECIDE-BY-ALGORITHM>
 #<STANDARD-CLASS MIDAS-INTERNAL:DECIDE-BY-ALGORITHM @ #x107c696a>
 #<STANDARD-CLASS ACTIVITY-SPACE:DECIDE-BY-RULE>
 #<STANDARD-CLASS ACTIVITY-SPACE:DECIDE-BY-RULE @ #x107b52da>)

This is happening throughout my heirarchy, not just on this class.  For
the sake of brevity, I am only including one example.  The others are
similar.  One has the normal object identification numbers after the
class name and the other(s) don't.  Yes, you can get more than two
classes with the same name.  The test above was run right after
recompilation of the files for the system to remove the metaclasses.  No
additional work other than the compiling and loading of the files was
done in this image.  

It is puzzling and disconcerting to say the least.  Thanks in advance
for your help.  
-- Marilyn
------------------------------------------------------------------
Marilyn Bunzo
Email: <eos.arc.nasa.gov at msb>             Company:  Sterling Software