🚀 go-pugleaf

"Tim Cross" <tcross@northnet.com.au> wrote in message
news:m3aehwgmco.fsf@tim.northnet.com.au...
> "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.
>

Totally

public class Coord implements Serializable {
    public final double x, y; // a co-ord is an "Immutable" class

    public Coord(double x, double y) { this.x=x; this.y = y; }

    public boolean equals(Object o) {
        if(!o instanceof Coord)
            return false;
        return x == ((Coord)o).x && y == ((Coord)o).y;
    }

    public int hashvalue() {
        long l;
        l = Double.doubleToLongBits(x) ^ Double.doubleToLongBits(y);
        return (int)(l ^ (l>>32));
    }

    public double distFrom(Coord c) {
        return Math.sqrt((x-c.x)*(x-c.x) + (y-c.y)*(y-c.y));
    }
}

--
--------------------------------------------------------------
http://www.users.bigpond.com/pmurray
ICQ: 26066755

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