Ideas:chad3f:RPFramework: Difference between revisions

Content deleted Content added

Inline

@@ Line 95: / Line 95: @@
 Benefits:
-- Guarantee order of creation.
+* Guarantee order of creation.
-- Compile-time parent checking (look ma' no strings).
+* 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 once, and everything else uses this value.
+* Never having to resolve RPClass's by name (in init code anyway), since the JVM will assign the runtime constaint 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).
+* 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).
 == Message Protocol ==

Navigation menu