Bug #5010
OO Quirk - Core.Collections.EntrySet
Status:
Hold
Priority:
Low
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Related issues
History
#1 Updated by Greg Shah over 5 years ago
- Description updated (diff)
From Marian:
RemoveAllmethod onCore.Collections.EntrySetonly removes entries present in input entry set if and only if entry key is equals with entry value. This is definitively wrong,Removeonly check entry's key.FWD implementation simply call
Removefor each entry and as such if key matches the entry is removed.
#2 Updated by Greg Shah over 5 years ago
- Parent task deleted (
#4384) - Status changed from Feedback to Hold
This is a bug. I see no reason to support it unless an application is encountered which relies upon this (heavily) for "correct" processing. Even if we find an app that is dependent, we will suggest the app code be fixed rather than relying upon this.
#3 Updated by Greg Shah over 5 years ago
- Related to Feature #4384: Builtin OO Implementation added
#4 Updated by Greg Shah over 5 years ago
- Related to Bug #5011: unimplemented OO 4GL quirks and bugs added
#5 Updated by Greg Shah over 5 years ago
- Related to deleted (Feature #4384: Builtin OO Implementation)