Re: Re: Re: Copying a hash to another hash problem

[demerphq]

i'm using numeric values for both keys and values

Well, this isnt intrinsically a bad thing. But more often than not it is.

The reason I say this is because if your indexes are sparse, ie 1, 500,623,7439,104029 or the like, then a hash is a much more suitable container type than an array is. (A hash would store the above usin 5 slots in a hash, an array would store at minimum 104029 elements.) However if the array is dense, 1..9,11..19,21..29 etc then an array is a more suitable approach. (Each slot in a hash is bigger than in an array, so even with the 4 wasted slots in the array would still be much smaller than the 26 allocated slots in the hash.)

Also, the difference isnt so much due to what you store in the values, but what you store in the keys.

Good luck and dont forget strict. :-)

--- demerphq
my friends call me, usually because I'm late....

[Anonymous Monk]

Maybe I should have given an explanation of my requirements.

Basically, I have a NAS setup with 700+ disks contained within 45 drawers split over 7 frames that I want to watch the temp on.
The code queries the drawers one by one and maps which drawers are in which frames and collects the current temp(also producing a pictorial map of the system).

So the array would only ever contain a max of (7) for the frames and (1-8) for the drawers within the frames (as not all frames have the same no. of drawers).

The copying (or snapshot) of the array was for comparing against the next time the prog went to check the temp to inform me of differences.

Cheers

Sean