On 5/25/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > jerry gay wrote: > > On 5/25/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > > i've added pop to ResizablePMCArray. i'll make sure the others are > > added and move on to FixedPMCArray next. > > Great, thanks. WRT fixed arrays - its a policy thing: do these map to > not resizable, not changable (Python tuples) or watever ... > i'll just stick to the resizable* variants for now, until the fixed* design is firmed up. until i run out of things to do. (hopefully design is done by then.)
as far as fixed* goes... are they immutable, or just unresizable? is there a need for both? and, what happens when errors (bounds, autovivify, etc.) occur? throw an exception? return undef pmc? return null? there are many questions to be answered. > >>These are several more or less independent steps, 1) and 2+3) can be > >>done in parallel. > > > BTW if you enter these as tickets into RT, we can truly have "takers." :) > > Yeah. As these are several steps, I'd like to have some takers first, or > interest, or ...Except the first item its more a long term plan. I don't > know if tickets really track it all. > i'd like to track my work using tickets. i suppose i could enter them myself, and track them that way, but i'm hoping the gods who sprang from zeus' forehead and rule this great flat land will provide us with all we need. ~jerry
