The impediments (the constraints and rules) of a programming language are there deliberately by design. They are the benefits. Among many other things, OO deliberately impedes a programmer from looking into the scope of objects unless specifically declared. This may be seen as an impediment to the programmer, who might just love to be able to bang anything out on the keyboard, but it is marketed as a long-term benefit to other programmers who later have to read the code.
Robert Howard Phoenix, Arizona -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marcus G. Daniels Sent: Tuesday, June 05, 2007 8:47 AM To: The Friday Morning Applied Complexity Coffee Group Subject: Re: [FRIAM] Fwd: ABM Douglas Roberts wrote: > When I mentioned that there were a few people on this list who felt > that OO methodologies were an impediment to ABM development rather > than a benefit, the general response was disbelief. OO methodologies, and esp. common OOP tools, can be both a benefit and an impediment -- the ratio of benefit and impediment depends on the situation. ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College lectures, archives, unsubscribe, maps at http://www.friam.org
