This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
strictfp is a keyword. You can modify a class declaration using the keyword final, abstract, or strictfp. You�re free to use strictfp in combination with abstract or final.
Marking a class as strictfp means that any method code in the class will conform to the IEEE754 standard rules for floating points. Without that modifier, floating points used in the methods might behave in a platform-dependent way. If you don�t declare a class as strictfp, you can still get strictfp behavior on a method-by-method basis, by declaring a method as strictfp.
Abstract methods also cannot be marked as strictfp.
Remember, strictfp forces floating points (and any floating-point operations) to adhere to the IEE754 standard. With strictfp, you can predict how your floating points will behave regardless of the underlying platform the JVM is running on. The downside is that if the underlying platform is capable of supporting greater precision, a strictfp method won�t be able to take advantage of it.
Instance variables cannot be marked strictfp.
Joined: Sep 01, 2005
Thanx Sampath And Raghvan for claring my doubt. I think it is necessary to only this much.Right?If so then Thanx u very much again [ September 29, 2005: Message edited by: agrah upadhyay ]