Ideas:chad3f:RPFramework: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Chad3f |
imported>Chad3f |
||
| (22 intermediate revisions by the same user not shown) | |||
| Line 99: | Line 99: | ||
* 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 |
* Never having to resolve RPClass's by name (in init code anyway), since the JVM will assign the runtime 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). |
* 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 == |
== Message Protocol == |
||
| Line 107: | Line 110: | ||
''TBW'' |
''TBW'' |
||
---- |
|||
[[Ideas:chad3f|Back to Ideas]] |
|||