Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Agilent Technologies sells a program called VEE that implements flow-based programming. Many non-programmers like it. Experienced programmers tend to prefer to write code. It is easy to draw a bowl of spaghetti!

The underlying implementation of VEE looks like LISP. If the underlying implementation was XML, it would be more stylish.

Circuit designers typically use flow-based design in the form of schematics. When circuit complexity gets high, schematics become problematic. The electronics industry solved this problem by converting almost all complex digital designs to Verilog or VHDL, which is code instead of flow.

Dominus tought a course in regular expressions that used flow-based diagrams to show flow in a regex. I thought it was helpful and intuitive. It would be nice to make such a tool for designing and documenting perl regexes, perhaps taking advantage of automatic graph layout with GraphViz.

Update By "underlying implementation," I mean that the program that does the work behind the scenes of the UI appears to be written in LISP. I surmised this because if you look at a VEE program file, it looks like LISP code.

Flow based diagrams help with visualization, but they do not work with large problems. Eventually the diagrams become too complex to see on the screen or print out. Hierarchical diagrams help with this, but do not solve the problem as well as a well-designed textual description. This is not an intuitive result. It was discovered when the diagrams became very large, such as happened when integrated circuit designs reached about 1_000_000 transistors.

It should work perfectly the first time! - toma

In reply to Re: Future of FBP by toma
in thread Future of FBP by jpm

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (6)
    As of 2017-11-22 03:54 GMT
    Find Nodes?
      Voting Booth?
      In order to be able to say "I know Perl", you must have:

      Results (314 votes). Check out past polls.