Re: An irrational coding choice found

I need a new approach to breaking me of this bad habit.

I bet that in the majority of your cases, it doesn't make any difference on whether you're using a hash or an array. Unless this access is 1) a bottleneck, 2) the current performance is unacceptable, and 3) changing it to an array makes the performance acceptable, then you've made the wrong choice.

Otherwise, it isn't worth fretting about.

Comment on Re: An irrational coding choice found

Replies are listed 'Best First'.
Re^2: An irrational coding choice found by Anonymous Monk on Mar 20, 2012 at 15:15 UTC
I concur; there is value to be had from learning how to get that last little squinch of performance out of a bit of code, but the actual doing-so should be saved for when you need it. The choice of an array-vs-hash for me frequently comes down to readability for myself and my teammates--someone else who isn't as skilled with Perl as I am will have to read this, so it needs to make sense. For the way we work, that usually means "hashes."	[reply]

Replies are listed 'Best First'.

Re^2: An irrational coding choice found
by Anonymous Monk on Mar 20, 2012 at 15:15 UTC

I concur; there is value to be had from learning *how* to get that last little squinch of performance out of a bit of code, but the actual doing-so should be saved for when you need it.

The choice of an array-vs-hash for me frequently comes down to readability for myself and my teammates--someone else who isn't as skilled with Perl as I am will have to read this, so it needs to make sense. For the way we work, that usually means "hashes."

[reply]