Out of all the ideas posted above, the one that resonates most
with me so far is the idea of using a hash instead of an array
for part of it. I would start here:
my @s = ( /([^(]+)(\([^)]+\))(.*)/ );
Using a hash would clarify what's being matched here (I'm not sure
myself. ). Maybe it would be something like this (using a hash
slice).
my @s{qw/table fields values/}) = ( /([^(]+)(\([^)]+\))(.*)/ );
that means that later on in the code you would be comparing
{fields} instead of [
1], which would be more intuitive. That
s usually a trigger point for me-- If I'm doing much with the
arrays by calling out specific positions like that, I usually ask
myself "would be clearer to use a hash here?".
Perhaps related, one of my favorite uses for hash slices at the
moment is to put the results of a DBI selectrow_array statement into
a hash in a single step like:
@row{qw/name company title/} = $DBH->selectrow_array("...");
-mark
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.