Conrad writes:
	>In the Ruby spirit of "there are better ways to do it", this might be
	>generalized by having a Ruby option that yielded an XML stream
	>representing Ruby's parse tree (and error info in the case of parse
	>errors), which could be used by smart checking modules. Then in
	>addition to a strict diagnostics module, other browser/IDE-related
	>modules could intelligently highlight/colorize troublesome usage,
	>suggest reasonable alternatives in some cases, and so on.

That could be quite interesing -- you could check for adherence
to the Law of Demeter, class fan-in and fan-out metrics, 
use of patterns and so on.

But I think there's also a need for a "strict" mode that
simply disallows highly questionable (non-OO) constructs.

/\ndy


--
Andrew Hunt, The Pragmatic Programmers, LLC.
Innovative Object-Oriented Software Development
web:   http://www.pragmaticprogrammer.com   email: andy / pragmaticprogrammer.com
--
Our New Book: "The Pragmatic Programmer" Published by Addison-Wesley Oct 1999
              (see www.pragmaticprogrammer.com/ppbook)
--