Michael Scott <[EMAIL PROTECTED]> wrote:
> So, to go back to Dan's original list, does that give us:
> (FixedMixedArray - fixed-size, mixed-type array)
> MixedArray - variable-sized, mixed-type array
> FixedPMCArray - fixed-size, PMC array
> PMCArray - variable-sized, PMC array
> FixedStringArr
On Sunday, January 25, 2004, at 06:10 , Michael Scott wrote:
On 25 Jan 2004, at 00:50, Gordon Henriksen wrote:
[...]
Is there something so terribly wrong with English? How about a general
scheme of * ? So, respectively,
MixedArray
Array
FixedArray
StringArray
FixedStringArray
Array is what Per
On 25 Jan 2004, at 00:50, Gordon Henriksen wrote:
[...]
Is there something so terribly wrong with English? How about a general
scheme of * ? So, respectively,
MixedArray
Array
FixedArray
StringArray
FixedStringArray
Array is what Perl familiars will usually want.
Did I miss something? What is A
On Friday, January 23, 2004, at 11:05 , Tim Bunce wrote:
Here's my preference:
*) ArrayFLenMixed - fixed-size, mixed-type array
*) ArrayVLenPMC- variable-sized PMC array
*) ArrayFLenPMC- fixed-size PMC array
*) ArrayVLenString - variable-sized string array
*) ArrayFLenString -
On Fri, Jan 23, 2004 at 02:19:37PM +0100, Michael Scott wrote:
> Is there a reason why the names have to be so terse?
>
> Mutable is not a bad word for able-to-change. (Cribbed from Cocoa,
> though there the immutability is absolute).
>
> *) Array - fixed-size, mixed-type array
> *) MutablePArra
At 2:19 PM +0100 1/23/04, Michael Scott wrote:
Is there a reason why the names have to be so terse?
No, I suppose not. Chalk it up to typing laziness, so the longer
names are certainly a viable option.
--
Dan
--"it's like
Is there a reason why the names have to be so terse?
Mutable is not a bad word for able-to-change. (Cribbed from Cocoa,
though there the immutability is absolute).
*) Array - fixed-size, mixed-type array
*) MutablePArray - variable-sized PMC array
*) PArray - Fixed-size PMC array
*) MutableSArra
At 2:15 PM -0500 1/21/04, Matt Fowles wrote:
All~
So, lets do the classes as:
*) Array - fixed-size, mixed-type array
*) vPArray - variable-sized PMC array
*) PArray - Fixed-size PMC array
*) vSArray - variable-sized string array
*) SArray - fixed-size string array
I suggest using "Array" to mean
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> *) Array - fixed-size, mixed-type array
> Personally I'd leave Array as it is, since it does one of the things
> that we need it to do.
Array isn't really mixed-typed. It has methods to store or retrieve
non-PMC types, but they are converted internally t
Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>4) list.c
> If you want to hack in on this, go ahead, though it looks like
> something that we'll ultimately need--its the guts of a sparse
> mixed-type array, which is useful and we may well need at some point.
Actually that was the reason, I implemented
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> So, lets do the classes as:
> *) Array - fixed-size, mixed-type array
> *) vPArray - variable-sized PMC array
> *) PArray - Fixed-size PMC array
> *) vSArray - variable-sized string array
> *) SArray - fixed-size string array
Actually I forgot one: We alr
*) Array - fixed-size, mixed-type array
*) vPArray - variable-sized PMC array
*) PArray - Fixed-size PMC array
*) vSArray - variable-sized string array
*) SArray - fixed-size string array
And so on, for N and I arrays. I'm not particularly attached to the
names. (Actually I think they suck, but th
Dan Sugalski writes:
> At 9:38 AM +0100 1/21/04, Leopold Toetsch wrote:
> >Dan Sugalski <[EMAIL PROTECTED]> wrote:
> >
> >> Okay, at this point we've a pile of different array classes
> >
> >> Before we go any further we need to figure out what we want.
> >
> >1) Unify setting/getting element count
All~
So, lets do the classes as:
*) Array - fixed-size, mixed-type array
*) vPArray - variable-sized PMC array
*) PArray - Fixed-size PMC array
*) vSArray - variable-sized string array
*) SArray - fixed-size string array
I suggest using "Array" to mean fixed size and "Vector" to mean variable
si
At 9:38 AM +0100 1/21/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
Okay, at this point we've a pile of different array classes
Before we go any further we need to figure out what we want.
1) Unify setting/getting element count
- the elements() vtable is unused (not acce
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Okay, at this point we've a pile of different array classes
> Before we go any further we need to figure out what we want.
1) Unify setting/getting element count
- the elements() vtable is unused (not accessible by opcode)
- we use get_integer()
At 2:17 PM +0100 1/11/04, Leopold Toetsch wrote:
> One further note, while at Array/PerlArray: the class dependency is
suboptimal. PerlArray isa Array isa list. The underlying list is
auto-extending and does no bounds checking. Array does bounds-checking.
PerlArray doesn't bounds check. So for
[ warnocked ]
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> The set_integer_native() vtable method of arrays is implemented
> inconsistently. The old historical way in Array was to set an initial
> size. My implementation in SArray OTOH only reserves the needed store,
> but doesn't change the eleme
The set_integer_native() vtable method of arrays is implemented
inconsistently. The old historical way in Array was to set an initial
size. My implementation in SArray OTOH only reserves the needed store,
but doesn't change the element count.
new P0, .SArray
set P0, 2
set I0, P0 # SA
19 matches
Mail list logo
