Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
native and abstract can't be combined because native means that it is implemented by a native library (dll) and abstract means that it must be implemented by a concrete java class.
strictfp is intended to modify the behavior of a single specific implementation, so it doesn't make sense to talk about a strictfp abstract method. Strictfp is not inherited.
synchronized + native is legal because then the native method has a lock on the object
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
Raju Champaklal wrote:then why is abstract+ strictfp legal for classes?
What is the use of putting strictfp modifier with an abstract method?? abstract method doesn't have any body, so there's no strict floating point calculations in it. Try to create an abstract method, and implement it in a sub-class and add structfp modifier to the implementation, it will compile fine. So basically abstract method which doesn't have strictfp modifier can be overridden by a method with strictfp modifier...