Changes between Version 23 and Version 24 of ArrayTasklist
- Timestamp:
- 02/04/10 20:38:58 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ArrayTasklist
v23 v24 22 22 Which behaviour is preferred? 23 23 * ''(Which types? Is this tied to the Resizable vs. Fixed? as an HLL author, I don't particularly care, as my language doesn't support straight negative indices anyway. If we're moving to unify this feature, I would again suggest we move to unify more, ala support of shift/push --Coke)'' 24 * ''(No, it's "random". ResizableBooleanArray does accept negative indeces, while ResizableIntegerArray does not.)''24 * ''(No, it's "random". ResizableBooleanArray does accept negative indeces, while ResizableIntegerArray does not.)'' 25 25 26 26 == Fixed Arrays == … … 53 53 * My dictionaries can't agree whether the spelling is "resizable" or "resizeable"; if the latter, should we fix the spelling now, later, or never? 54 54 55 == Deprecation of Array ==55 == Universal Ancestral "Array" == #ArrayAncestor 56 56 57 Several commentators have said that Array should be removed. 58 59 What, if anything, is it useful for? 60 What's the difference between "Array" and "ResizeablePMCArray" or "FixedPMCArray"? 61 (A note on [http://rt.perl.org/rt3/Ticket/Display.html?id=56718 RT#56718] says that its only useful feature is its sparseness.) 62 63 What needs to be done before it can be removed? 57 It has been suggested (in #1416) that we should have a common ancestor class for all array-like types, to facilitate adding new common methods to them all. Perhaps a better alternative would be multiple "base classes" representing the various aspects of an array (see [#Roleseparation next section]). 64 58 65 59 == Role separation ==