-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 12
-
b02
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8243382 | 11.0.8-oracle | Kim Barrett | P4 | Resolved | Fixed | b04 |
JDK-8244995 | 11.0.8 | Kim Barrett | P4 | Resolved | Fixed | b04 |
The review of JDK-8204097 showed that the "allocate list" nomenclature used internally in OopStorage is confusing. It should have been "allocation list". Make the following name changes throughout the implementation of OopStorage:
AllocateEntry => AllocationListEntry
AllocateList => AllocationList
_allocate_entry => _allocation_list_entry
_allocate_list => _allocation_list
allocate_entry() => allocation_list_entry()
allocate_list() => allocation_list()
-- these functions are particularly confusing, since they don't
allocate anything.
AllocateEntry => AllocationListEntry
AllocateList => AllocationList
_allocate_entry => _allocation_list_entry
_allocate_list => _allocation_list
allocate_entry() => allocation_list_entry()
allocate_list() => allocation_list()
-- these functions are particularly confusing, since they don't
allocate anything.
- backported by
-
JDK-8243382 Fix confusing "allocate" naming in OopStorage
-
- Resolved
-
-
JDK-8244995 Fix confusing "allocate" naming in OopStorage
-
- Resolved
-
- relates to
-
JDK-8204097 Simplify OopStorage::AllocateList block entry access
-
- Resolved
-