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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|