Don't be so harsh. There is a difference between this being not a good idea, and the idea not be cost effective for the folks who have to implement it.
I would tend to agree that this is something that would be great in the OpenAPI (assuming the OpenAPI is that open). But I wouldn't dismiss the idea as being ridiculous either. When javadocs are riddled with misspellings and grammatical mistakes it makes it that much more difficult to maintain the code. The javadoc are the first line of maintenance, so anything that encourages my engineers to write better javadocs is a long-term plus. If you don't write javadocs, then there isn't an issue. Presumably any such feature (openAPI or not, could be disabled). And in regards to the expected "bloatware" argument, I could (and would) make the argument that EJB and CVS support are bloatware because I don't use them. But I understand that there are others who do. Just like you wouldn't use a spell checker, doesn't meant there aren't others out there who would. Mike On 27 Mar 2002 at 18:08, Ian Pojman wrote: > Just because people like you want pop machine integration and mp3 > playing and spell checking doesnt make them good either. How is it a > good code analysis function? You obviously dont understand the > resources involved in implementing it. Also - If you can't type in > strings right, you shouldn't be programming. It's just not a practical > idea at ALL. Especially with OpenAPI on the table. --- [EMAIL PROTECTED] To obtain my PGP public key, mail "SEND PUB KEY" in the subject to "[EMAIL PROTECTED]" _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
