Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!igor!rutabaga!jls From: jls@rutabaga.Rational.COM (Jim Showalter) Newsgroups: comp.object Subject: Re: Which OOPL is the best? Message-ID: Date: 27 Mar 91 03:48:41 GMT References: <1991Mar25.045952.813@agate.berkeley.edu> Sender: news@Rational.COM Lines: 23 >Just how can I enforce a >particular OO method once I've decided what is right for me? Good question. This is where language simply runs out of steam, and the OTHER 95% of the problem rears its ugly head. This is where process, methodology, community hygiene, tool support, etc are all dominant concerns. While I do believe that implementation rules (e.g. no gotos) can help at the micro-level (and can even be enforced with a tailorable compiler [we sell one for Ada]), they don't mean diddly at the architectural/design level. I've seen projects jump into OO all happy and smiling and then fall over dead because they didn't change their paradigm, their management structure, their way of assessing progress ("Hey, start typing: we need to get our SLOC rates up!"), their accounting system (SLOC = money), etc etc etc. These infrastructural issues are so daunting they dwarf mere language issues...which may explain why so many people are content to focus on just the language issues--it's EASIER! -- ***** DISCLAIMER: The opinions expressed herein are my own. Duh. Like you'd ever be able to find a company (or, for that matter, very many people) with opinions like mine. -- "When I want your opinion, I'll read it in your entrails."