|Don't ask to ask, just ask|
Best Practice for Lots of Static Databy SirBones (Friar)
|on Dec 01, 2006 at 02:45 UTC||Need Help??|
SirBones has asked for the
wisdom of the Perl Monks concerning the following question:
Greetings all. I have a "best practices" question. What's the best way to deal with an annoying amount (from a source file maintenance point-of-view) of static text data?
I have a utility that does some data analysis on returned bit strings coming from various devices under test; one of the things it does is translate the bits that are "on" to their text meaning. For example, I might get a bit string from "device1" which looks like:
And so on, sometimes for several hundreds of bits. I've been keeping the meaning of the bits in various arrays:
And when I walk through the bit string, it's simple enough to display the state of things:
There are a number of possible devices, and each device has a different set of information specific to it. So sometimes I've been combining the labels into a hash of arrays:
In any case, things have become very unwieldy in my source file. I have hundreds of lines taken up with these lists, and it will eventually number thousands. I know there must be a better way to organize this. I can think of some possibilities to separate the data and the code; I'm sure there are others:
I'm curious as to how those folks with more experience in production level Perl apps would handle this.
"This bounty hunter is my kind of scum: Fearless and inventive." --J.T. Hutt