I think that you want to parse the string the same way that a shell parses a command-line. The result is a list of sub-strings. It probably is a good idea to do the validation (use previous suggestions) before attempting the parse. I cannot think of a good way to do the parsing. I hope I have put other monks on the right track.
UPDATE
You can parse the strings with Text::CSV
#!/usr/bin/perl
use warnings;
use strict;
use Text::CSV;
my @strings = (
'"my" "dog"',
'"my" "dog shepherd"',
'my dog',
'my "dog shepherd"',
'"my "dog"',
'my "dog shepherd',
);
my $csv = Text::CSV->new ( {sep_char => ' '} )
or die "Cannot use CSV: ".Text::CSV->error_diag ();
foreach my $string (@strings){
open my $fh, '<', \$string or die "Cannot open string";
if (((my $temp = $string) =~ tr/"//) % 2){
warn "invalid string";
next;
}
my $row = $csv->getline($fh);
if (!defined $row) {
warn "getline failed";
next;
}
close $fh;
$" = ' | ';
print "@$row\n";
}
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.