The paper is more approachable by computer scientists

Hm. "Approachable"? Makes it sound like I might be intimidated by the other paper. I'm not. I'm disgusted by it.

It annoys me that academia continues to require that thesis be written in such an obfuscated manner; that they continue to emphasis form over content; that thesis writing has become an art-form an end unto itself, devoid of purpose beyond impressing the promoters of that art.

The purpose should be to: describe a problem, the history of that problem, a (new) approach to solving it, and the analysis of that solution; as clearly and simply as possible. But it is rarely ever done that way.

the original paper by Alfred Aho(1981, SIAM journal of computing) on which my research is based.

I've only given it a once over so far, but frankly, it does not seem any better to me. Presumably, as you've come back here looking for help, you don't get it either.

The procedure on the second page that purports to be an "algorithm description" is nothing of the sort. It is more of a "wish list". It is the equivalent of calling the following a recipe for a Lemon Meringue Pie:

  1. Make some pastry;
  2. Fill it with some lemon filling;
  3. Top it with some meringue;
  4. Cook it.

Maybe the details are described somewhere in the pages of words; but

The algorithm may or may not be good; but the description is utter meaningless garbage.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong


In reply to Re^5: supertree construction in perl by BrowserUk
in thread supertree construction in perl by zing

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.