From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2ea02452876a15e1 X-Google-Attributes: gid103376,public From: Bob Crispen Subject: Re: Real OO Date: 1996/05/02 Message-ID: <9605021325.AA03354@eight-ball>#1/1 X-Deja-AN: 152657282 sender: Ada programming language comments: Gated by NETNEWS@AUVM.AMERICAN.EDU newsgroups: comp.lang.ada Date: 1996-05-02T00:00:00+00:00 List-Id: Richard Riehle sez: >Robert Dewar (dewar@cs.nyu.edu) wrote: [snip] >: P.S. spaghetti code doesn't just mean code you don't like. It is a rather >: specific term used to described the non-nested chaotic control structures >: caused by undisciplined use of gotos or equivalent transfers of control. >: I think it is useful to keep this sense. > > HmmmMMMMMMmmmmm. I guess we could characterize OOP as "ravioli code" > rather than spaghetti code. Each class is a little square of pasta > enclosing the encapsulated delicacies. And often with about as much internal structure as a plate of ravioli. Good metaphor. > Anyone for Pizza code? Dump a side order of spaghetti on top of a pepperoni pizza and you get a perfect representation of what some new kids draw when I ask them, "Draw me a picture of your main system elements and the dataflows between them." -- shortly before they pick up the paper and say, "Uh, let me get back to you on this." Don't forget pasta fazool code, where the subprograms and processes intercommunicate through a bowl of variable soup (shared memory). Preferable to all of these is spumoni code -- or at least the kind of spumoni you can get in Alabama (often spoken of as "little Italy" by people who are severely geographically impaired) where the ice cream looks exactly like those diagrams of Unix. Bob "Vito" Crispen revbob@eight-ball.hv.boeing.com Speaking for myself, not my company