Thanks,
I see the startup actions. It almost did what I wanted. What I have ended up doing ( and maybe this is bad ), is to make my file method look like this:
sub file {
my $self = shift;
my $file = shift;
our $object;
$object = $self;
if ( not -f $file ){ carp 'Invalid filename provided' };
my @grammer = <DATA>;
my $grammer = join ' ', @grammer;
my $parser = Parse::RecDescent->new( $grammer );
open my $file_h, '<', $file or croak q{Couldn't open file};
while ( my $line = <$file_h> ){
chomp $line;
$self = $parser->startrule($line);
}
close $file_h;
undef $object;
return $file;
}
And all of my grammers use this syntax:
Klarf::1_8::_store_line( $Klarf::1_8::object, $item{LINE}, 'col' )
I will work on removing the hard coded package links if possible.
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.