I've done work on converting from graph form to text form. (Well, technically, I went from graph to a parse tree, but it's trivial to convert the parse tree into something with the syntax of "specimen 2".) Check out the working code at Parsing 2D Graphs and the Parse::RecDescent version. (Update: I just noticed you link to these indirectly through castaway's post.) It wasn't easy, but it handles choices and loops. The problem with it is that it expects valid data. Adding error checking is doable, but it would take time. Feel free to use any or all parts of it, and feel free to ask me any questions, given how poorly it is documented.

In reply to Re: Diagram to Text and Vice Versa (DAG, RTN) by ikegami
in thread Diagram to Text and Vice Versa (DAG, RTN) by dimar

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.