I wasn't talking about the situation where you proudly show your design in a conference room using a spiffy powerpoint presentation.
Nor was I. I was addressing the point that heavy OO is hard to work through because the complete design is scattered throughout a large number of files. UML helps here because even a crappy design will at least show all the crap in one place, provided the code matches what is in that diagram.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
In reply to Re: Re: All in one
by hardburn
in thread All in one
by duff
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |