campus1plb:

  1. I'd create the columns during runtime: that way, if someone adds a new subject, you don't need to change your program.
  2. Either data structure is fine. I'd personally go with a hash table, but only because that would feel more natural for me. If you're comfortable with an array, go with it.

Your third question is the fun part. I don't find that writing the regexes is that difficult. The problem is more 'are you sure you're getting everything correctly?'.

I generally attack it like this: write regexes for the first 5 or ten lines of data. Then make a program to match and delete all the requirements that it can. Then look at the next few lines of what's left, and add new regexes and/or altering existing ones. After a few iterations, you'll have regexes that can handle most of the data. You may have a few stragglers (misspellings, etc.) that may require a bit of playing with. You might, for example, first repair misspellings before matching requirements.

Have fun with it!

...roboticus

When your only tool is a hammer, all problems look like your thumb.

In reply to Re: CSV regex with hash/array program plan by roboticus
in thread CSV regex with hash/array program plan by campus1plb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.