Feature #1716
remove unnecessary wrapping/unwrapping for expressions where primitive results could be used directly
Start date:
Due date:
% Done:
0%
Estimated time:
24.00 h
billable:
No
vendor_id:
GCD
History
#1 Updated by Eric Faulhaber over 11 years ago
Examples:
- when a CompareOps method is used directly in a control flow statement such as IF, rework the method name into one which returns a boolean to avoid the need to wrap in CompareOps and then unwrap in calling code;
- allow fields and wrappers (vars) to be compared directly from primitive Java types (e.g. int); this can be done easily with character and String but there is probably value in overloading the equals() and compareTo() methods... CompareOps and other changes may be needed too;
- allow fields and wrappers (vars) to be assigned directly from primitive Java types (e.g. int).
These improvements may all require the BaseDataType class to have the knowledge of the logical class removed if the unknown value testing does not need to be there anymore
#2 Updated by Greg Shah over 11 years ago
- Target version set to Code Improvements
#3 Updated by Greg Shah over 7 years ago
- Target version changed from Code Improvements to Converted Code Improvements - Deduplication