> I totally disagree with just about everything Noel said except for the
> end.
> As long as everyone understands that documentation is as important as
> code and that poorly documented code is just pure rat dung.
> Code complete, means docs too.
That may be your philosophy, and it might even be one that I share. But
we're not the ones being screwed. The end users are. You want to incent
developers, find another way. But I suggest that at the moment, Peter is
doing a great job of fixing years of neglect.
> Noel, you're wrong
No, I'm pragmatic and you just don't like it. This isn't about some ivory
tower notion of what makes good code. This is about lots of James users who
are stuck using buggy code and bad documention while we sit here using the
good stuff and arguing over when to deliver it to them.
> What good is a release to a user if he can't make hide nor hair of it?
> If I weren't a semi-decent Java developer I couldn't even set up JAMES.
I agree with you, but what does this have to do with javadocs, Andy? Talk
about end user documentation and we'd be agreeing, because what good are
javadocs to the average user?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
