The COM code in VW uses a class called Tools.Note. Unfortunately, none
of the references qualify the class with the namespace. They just reference Note directly. In a client application I've been upgrading to 7.7, they have a domain class called Smalltalk.Note. This means that COM binds to the Smalltalk.Note class instead of Tools.Note. We had to go in to all the COM classes and change Note to Tools.Note. Is there any way this could be changed in the base VW code for COM? Thanks, David Buck Simberon Inc. www.simberon.com _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
David,
I do not foresee a change in VisualWorks COM ever. It is not good design to put application code in namespace Smalltalk (since VisualWorks 5i). The right solution is to move all customer classes to a customer proprietary name space. Georg Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812 Tel. +49-3496-214328, Fax +49-3496-214712 > -----Ursprüngliche Nachricht----- > Von: [hidden email] [mailto:[hidden email]] Im > Auftrag von David Buck > Gesendet: Sonntag, 8. August 2010 21:25 > An: 'VWNC' > Betreff: [vwnc] COM use of Note class > > The COM code in VW uses a class called Tools.Note. Unfortunately, none of > the references qualify the class with the namespace. They just reference > Note directly. > > In a client application I've been upgrading to 7.7, they have a domain > called Smalltalk.Note. This means that COM binds to the Smalltalk.Note class > instead of Tools.Note. We had to go in to all the COM classes and change > Note to Tools.Note. > > Is there any way this could be changed in the base VW code for COM? > > Thanks, > > David Buck > Simberon Inc. > www.simberon.com > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Well, one would think that the same criteria ought to apply
to the COM code. It is defined, not quite in Smalltalk, but in places
like Smalltalk.External and in Smalltalk.Tools which are imported into
the Smalltalk namespaces, and it relies on resolving those references
through Smalltalk. So equally, COM should perhaps be using its own
namespace, and not defining names such that
Smalltalk.Note resolves to an internal COM class, and that COM functionality depends on it doing so. At 03:55 PM 2010-08-08, Georg Heeg wrote: David, --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |