Why is using object-oriented Perl an entirely separate manner of organizing a large project? Any one of the three preceding categories could be implemented using OO Perl, or non-OO Perl, or C, or lisp, or ... .

Hmmm, good point.

It is common to speak of n-tier client/server applications (I'm working on one now).

Hmm, so what I have is a type of tiered application. A inward spiraling tier: program A calls B calls C which does the inner work then we pop back to B then back to A.

Thanks for your comments. I had hoped to generate a lot of discussion.

Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality