Revision as of 22:59, 24 October 2016 edit 99.236.6.160 (talk) →‎Metaobject protocol ← Previous edit		Revision as of 16:18, 27 November 2016 edit undo 184.151.190.247 (talk) →‎Runtime and compile time Tags: Mobile edit Mobile web edit Next edit →
Line 15: When compilation is not available at run-time there are additional complications for the implementation of metaobject protocol. For example, it is possible to change the type hierarchy with such a protocol but doing so may cause problems for code compiled with an alternative class model definition. Some environments have found innovative solutions for this, e.g., by handling metaobject issues at compile time. A good example of this is [[OpenC++ (software tool)\|OpenC++]].<ref>{{cite journal\|last=Chiba\|first=Shigeru\|title=A Metaobject Protocol for C++\|journal=OOPSLA '95\|year=1995\|url=http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.15.7049\|accessdate=27 December 2013}}</ref> It is noteworthy that the [[Semantic ~~web~~Web]] object-oriented model is more dynamic than most standard object systems, and is consistent with runtime metaobject protocols. For example, in the Semantic ~~web~~Web model classes are expected to change their relations to each other and there is a special [[inference engine]] known as a classifier that can validate and analyze evolving class models.<ref>{{cite web\|url=http://www.w3.org/2001/sw/BestPractices/SE/ODSD/\|title=A Semantic Web Primer for Object-Oriented Software Developers\|last1=Knublauch\|first1=Holger\|last2=Oberle\|first2=Daniel\|last3=Tetlow\|first3=Phil\|last4=Wallace\|first4=Evan\|publisher=[[W3C]]\|date=2006-03-09\|accessdate=2008-07-30}}</ref> === Usage ===

Metaobject: Difference between revisions