Re^2: can i avoid all these nested hashes

That's clumbsier, slower, and uses 4 times as much memory.

You're sugesting replacing one line of built-in code

$snp{'Gene1'}{'Trans1'}{'color'} = 'blue';
[download]

with

my $snp1  = SNP->new(id => 'SNP1');
my $gene  = $snp1->addGene('Gene1');
my $trans = $gene->addTranscript('Trans1');
$trans->setProp(big   => 1);
[download]

Plus 70 lines of code that does nothing more than replicate built-in functionality. More code, means more bugs.

The very definition of assinine.

Comment on Re^2: can i avoid all these nested hashes Select or Download Code

Replies are listed 'Best First'.
Re^3: can i avoid all these nested hashes by graff (Chancellor) on Dec 13, 2010 at 04:32 UTC
At first glance, what Grandfather did above looks a lot like "copy/paste" coding, and maybe even "OOP for OOP's sake". But you don't have to look all that closely at his code, and you don't have think very long about the domain of the problem, to understand that Grandfather is actually making a smart investment up front, in anticipation of what could end up being a fairly diverse set of problems to be addressed. I'm all for using expedients whenever possible, and I would have probably used BrowserUK's approach myself, if I knew that there was just the one question to be answered (and quickly) about the data. But putting in a foundation for future work is not "assinine" [sic].	[reply]
Re^4: can i avoid all these nested hashes by Anonymous Monk on Dec 13, 2010 at 09:07 UTC
Ask your average haulier if it is a "sound investment" to send a 8mpg 18-wheeler to pick up a 1/4 tonne of goods from a new customer, in antisipation that they might become a 25-tonne per trip customer sometime in the future.	[reply]