It doesn't matter how you start. If making a decision really bothers you, you could write each option into a suitably sized box drawn on a piece of paper, then throw a dart at it and choose a technique that way. However, once you start coding you'll generally pretty quickly find what doesn't work and why. Then you can make a somewhat better informed decision (perhaps by eliminating some options from the decision tool?).
When you have some code to show (any code, but be sensible) then it is time to come back and help refine it.
As a general rule though, use a hash when you need to look stuff up and an array when you don't need to look it up, but do need to keep it together and possibly need to retain its order. For more complicated stuff just apply the rule iteratively: 'I need to look something up to get a list of values = hash of array'.
In reply to Re: ISOLATE 2 ASSOCIATED FIELDS IN A TEXT FILE, then CONVERT the first into another based on a table of definitions
by GrandFather
in thread ISOLATE 2 ASSOCIATED FIELDS IN A TEXT FILE, then CONVERT the first into another based on a table of definitions
by mupud
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |