Changes between Version 11 and Version 12 of ArrayTasklist

Show
Ignore:
Timestamp:
10/13/09 17:17:23 (5 years ago)
Author:
kurahaupo
Comment:

notes on applicability of uninitialized resizable arrays; more details on "fully general" arrays

Legend:

Unmodified
Added
Removed
Modified
  • ArrayTasklist

    v11 v12  
    2727== Resizable Arrays == 
    2828 
    29  * Do any HLL's use the current resizable array types without extending them to include initialization of unset elements? (Yes, partcl, at the moment, uses RPAs without extending them to deal with potentially unset elements --coke) 
     29 * Do any HLL's use the current resizable array types without extending them to include initialization of unset elements? 
     30   * (Yes, partcl, at the moment, uses RPAs without extending them to deal with potentially unset elements --coke) 
     31   * ResizablePMCArray, ResizableStringArray and ResizableBooleanArray already do initialization of elements; this question is really about making ResizableIntegerArray and ResizableFloatArray work the same way. 
     32   * (The Regex engine uses ResizableIntegerArray somewhere -- I'm not sure where, but the compiler died when I had a broken version under development --kurahaupo) 
    3033 
    3134 They were created as extensions of fixed-sized arrays, extended to support pop, push, shift, unshift and set-integer, but ''not'' extended to guarantee initialization. However it seems likely that the lack of initialization is a misplaced optimization that is probably of no use to any HLL, forcing every HLL to override this behaviour. Does anyone implementing a language say otherwise? 
     
    4043 
    4144 * A general-purpose resizable array would need these attrs: 
     45   * element_type (int8, int16, int32, int64, int128, float32, float64, float128, string, pmc) 
    4246   * allocated_size 
    4347   * initialized_size