Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • > I think substituting 'messages' for 'tables' preserves the meaning while bringing it forward into what seems to becoming a service-driven era.

    "Tables" is more like "data structures". Messages are APIs, that is, "flow charts".
    • Maybe I'm misinterpreting, but I read the quote as saying that with only flowcharts and no data you'd be hard pressed to figure out what an application actually does. With messages -- including the message name and the data accompanying a message -- I think you can get a very clear picture of what an application does.

      It doesn't apply in all cases, but IME it's been more useful in the applications I've been working on for the last five years, particularly when you consider that people can hide crappy datab