Ideas:chad3f:RPFramework: Difference between revisions

Content deleted Content added

Revision as of 02:47, 31 May 2007 view source imported>Chad3f m →Message Protocol ← Older edit		Latest revision as of 02:52, 31 May 2007 view source imported>Chad3f →Message Protocol
(18 intermediate revisions by the same user not shown)
Line 99: * Compile-time parent checking (look ma' no strings). * Never having to resolve RPClass's by name (in init code anyway), since the JVM will assign the runtime ~~constaint~~constant once, and everything else uses this value. * No explicit need to force class definition from a common setup class/method, as long as the class containing the RPCLASS constant is referenced before any RPObject instances using that class are bound to their RPClass. And this can be guaranteed if the constant is used when setting the RPObject's class (with the same benefits as RPClass gets). Line 105: ---- == Message Protocol == Line 111 ⟶ 110: ''TBW'' ---- [[Ideas:chad3f\|Back to Ideas]]