🚀 go-pugleaf

"Paul Murray" <pmurray@nospam.bigpond.com> writes:
[snip]
 
> On a more general note, you might be better off using the Collections API
> rather than explicitly putting things in arrays. If you do that, you may as
> well use a class for a floating-point XY coord. This allows you to attach
> methods etc. java.util has integer Point and Dimension classes - why not
> model your floating-point classes on those?
> 
I think Paul is spot on here with this advice. Create your own classes
to represent your coordinates and this will give you much better data
encapsulation. As Paul points out, it will also allow you to associate
methods with this data. For example, you might be able to add a
distance method to your coord class which, when passed another coord
object returns the distance/metric between the two points etc. There
is also less chance of your system becomming inconsistant which could
happen if one of your arrays is updated and the other isn't etc. 

Tim

 

-- 
Tim Cross
NorthNet Internet Services
mailto:tcross@northnet.com.au
phone:+61 2 6772 5973