Threads not marked as deprecated

[dranonymous]

I am using threads in an app I'm writing and recently discovered I was 'pausing' them the wrong way.  When you look at the javadoc it says Thread.suspend() as deprecated, but when you compile with the deprecation warnings on, no warnings are generated.  This makes me think they wrote the javadoc text, but didn't actually mark the methods that way.  The other tip off is the individual method names don't have a since tag to them or show the normal deprecated text in the javadoc.

Can anyone confirm this?  Are there other situations where the methods aren't marked?

Regards,
Dr. A>

[blahblahblahh]

The javadoc text comes DIRECTLY from the source code - that is, in fact, the entire point of javadoc, to be precisely accurate.

So I can only guess that you are using some broken distribution, or are using javadocs from a version different than the one you are running.

I certainly get deprecation warnings on the thread methods, so ...

[dranonymous]

Well, just yesterday in fact, a friend and I were looking at this.  Turns out eclipse 2.x is acting dumb.  I've set the prefs to give an error on any deprecated methods I try and use, but it never registers anything.  The other warnings/errors show up fine.

Any ideas?

Dr. A>

Games published by our own members! Check 'em out!

[Malohkan]

I have an idea... upgrade to 3.0 or 3.1  3.0 is practically bug free except when you upgrade (or at least when I did) to Windows XP Service Pack 2, it will no longer be usable.  3.1 is SLIGHTLY buggy as I've found, since there's no official release yet, but it works under Service Pack 2.  But at any rate, you no longer have an excuse to use 2.x

3.0 M8 was the build I was using of 3.0, and I never found a bug in it until I found it couldn't run with SP2.  I think that'll be your best bet if you're worried about problems.