Inner class gives you the conveinence of accessing all the members of parent class but it is not highly reuseable. So from the reusability perspective, inner class is not a good choice. However, it is very suitable to be used as the event listener in the parent class, especially in the UI development using awt or swing.
"Jon D. Hatton" <[EMAIL PROTECTED]> on 02/26/2003 11:07:21 AM Please respond to "jdjlist" <[EMAIL PROTECTED]> To: "jdjlist" <[EMAIL PROTECTED]> cc: Subject: [jdjlist] Inner class I have the need to use an inner class and Im curious if there is any advantage to doing this over just making a new seperate class..putting aside the encapsulation issues of course. My usage of this inner class is a simple structure to support some specific functionality in the parent class.. ie. a timer collection of current timers in process.. Thanks for any comments --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] http://www.sys-con.com/fusetalk ******************* PLEASE NOTE ******************* This E-Mail/telefax message and any documents accompanying this transmission may contain privileged and/or confidential information and is intended solely for the addressee(s) named above. If you are not the intended addressee/recipient, you are hereby notified that any use of, disclosure, copying, distribution, or reliance on the contents of this E-Mail/telefax information is strictly prohibited and may result in legal action against you. Please reply to the sender advising of the error in transmission and immediately delete/destroy the message and any accompanying documents. Thank you. --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] http://www.sys-con.com/fusetalk
