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.

use Perl

All the Perl that's Practical to Extract and Report

An addition to Brooks More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Errrm, I think not. (Score:2)

by jhi (318) <jhi@iki.fi> on 2006.08.28 9:55 (#49628) Homepage Journal

> 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".

Reply to This
- Re: (Score:2)
  
  by lachoy (1663)
  
  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

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.