IMHASO, (...And Sober...)
I wouldn't get worried about the fact that intersect operates on more than one Line. So does 'equals' - you just take another member of the class as an arg and its all quite natural.
As I suspect you think too, the Helpers idea is barbaric. Why use objects at all in that case?
So one OO way to do it (in pseudo-code definitions) would be:
->new( Point p1, Point p2, ... );
->has_inside( Point p ); # return true/false
->get_outside_point(); # return Point outside the polygon
->first_line(); # return 'line 1' - reset counter
->next_line(); # return next_line, incr counter
# undef if no more
->new( Point x, Point y );
->intersects( Line l ); # return true/false
# Is this what you mean by 'same_line'?
->equals( Line l ); # return true/false
Lastly, I like to name 'private' methods with a leading underscore. So if ->same_line or ->equals is really only needed by ->intersects you might want to rename it to ->_equals.
(This is just documentation obviously. Anyone with the MilliClue (or KiloClue) who wishes to violate the published API is free to. This is perl, after all.)
However, in this particular case it seems like a sensible function to have as part of the object's "published" API and so I probably wouldn't do it.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.