Changes between Initial Version and Version 1 of Ticket #1309, comment 8
- Timestamp:
- 12/15/10 09:16:18 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1309, comment 8
initial v1 16 16 }}} 17 17 18 Now, I certainly could catch the exception in my code, but this implementation would make it possible to break other plugins by introducing types without parameterless constructors. In my opinion either the `ApplicationManager` should catch the exception (1), or types which must not be discovered should be attributed with something like `[Undiscoverable]` (2). 18 Now, I certainly could catch the exception in my code, but this implementation would make it possible to break other plugins by introducing types without parameterless constructors. In my opinion either the `ApplicationManager` should catch the exception (1), or types which must not be discovered should be attributed with something like `[Undiscoverable]` (2). Or we just make `RealVectorAdditiveMoveWrapper ` Storable (3). 19 19 20 20 (1) has the disadvantage that types which accidentally have no parameterless constructor can be introduced without any warning. … … 22 22 (2) would force the developer to think about the type discovery mechanism which i think is OK for types which should explicitly ''not'' be discovered. 23 23 24 (3) ok, if the scenario that a type should not be discoverable is really rare.
