http://www.nomachetejuggling.com/2006/08/23/globals-in-java/ Rod Hilton's rants about stuff he cares about way too much. Sat, 28 Jan 2012 12:01:26 +0000 hourly 1 http://wordpress.org/?v=3.2 http://www.nomachetejuggling.com/2006/08/23/globals-in-java/comment-page-1/#comment-2257 abhi Sat, 02 Sep 2006 15:35:29 +0000 http://blog.air0day.com/2006/08/23/globals-in-java/#comment-2257 I may be wrong here, but the main reason why static imports were called upon was that the only other way of including common data (interface implementation) made it (the data) a part of the classes public API. We ARE sidestepping that issue with static imports, and also, the qualification of the class name in the import statement means that there's still a line between global data and utility constants, no matter how thin. This means that the programmer take the responsibility of making sure the client doesn't get direct access to that data. To mantain the sanctity of OO principles, just don't use static import, unless absolutely nessecerry. I may be wrong here, but the main reason why static imports were called upon was that the only other way of including common data (interface implementation) made it (the data) a part of the classes public API. We ARE sidestepping that issue with static imports, and also, the qualification of the class name in the import statement means that there’s still a line between global data and utility constants, no matter how thin. This means that the programmer take the responsibility of making sure the client doesn’t get direct access to that data. To mantain the sanctity of OO principles, just don’t use static import, unless absolutely nessecerry.

]]>