By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,369 Members | 950 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,369 IT Pros & Developers. It's quick & easy.

AspectJ... hasChanged aspect?

P: n/a
Is this a good idea? I would like to know when some of my objects
have changed. Would it a) be a good idea to write this as an aspect
rather than cluttering classes. b) what would be the best way to
write it? My plan is to add a boolean and method for hasChanged and
set this boolean based on the value of the the input to the setter
methods compaired with the current value of the coresponding getter

If there is a better way of doing this I would like to hear it,
however it does nicely remove an added level of complexity from many
methods in my system.

I'm new to aspect oriented programming but it certainly seems to me to
be a massive step forward in designing software.
Jul 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.