You might consider writing a parser which is just "good enough" for the files you want to process. Since structures seem to end on line boundaries, you can try something like this:
my $root = {};
my @stack;
my $object = $root;
use Data::Dumper;
while (<DATA>) {
if (m{^\s*\/\*}) { next } # assume single line comment
elsif (m/^\s*END(_OBJECT)?/) {
$object = pop(@stack);
} elsif (m/^\s*OBJECT\s*=\s*(\S+)/) {
my $new = { parent => $object, type = $1 };
push(@{$object->{children}}, $new);
push(@stack, $object);
$object = $new;
} elsif (m/^\s*(\w+)\s*=\s*(\S*)/) {
my $property = $1;
my $value = $2;
if ($value =~ m/^"/) {
while ( (($value =~ tr/"//) % 2 != 0) && defined($_ = <DATA>)) {
s/^\s*//;
$value .= $_;
}
}
$object->{$property} = $value;
}
}
print Dumper($root);
The string literal parsing is admittedly a little cheesy since I don't know what the rules are for representing literals in ODL files.
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.