You know, I think you might have nailed it. Intuitively that seems correct.

I did it this way to divide the parsing of the input file from the format of the output. So the backend would say "I've found a glark element", and frontend A may say "Ignore it", while frontend B may say "Concatenate it with the preceding output".

The plan was for the client to say:

my $obj = Backend->new(frontend=>FrontendClass);

[download]

But, as you point out, far more sensible is for them to say:

my $obj = Frontend->new;

[download]

Then to have Frontend use Backend. :-) Thank you very much!

In reply to Re^2: OO Parser Class with Callbacks - Confusion by Anonymous Monk
in thread OO Parser Class with Callbacks - Confusion by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.