RE: [Rails-devel] Suggested object model for core generic framework

[Brett L. <wak...@ea...>]

I like just calling it a stop, or a trainStop.

What do you think about this layout:

Have an interface, or abstract class called TrainStop, which defines=
 objects for which a train must stop during the course of its runs. Cities,=
 towns, and whistle stops (e.g. the single 10$ stops, the 1830 rules book=
 calls 'em cross-bars) are all derived from the interface/abstract class.

This way, when we're calculating routes, we can just pull together all the=
 objects on the map that are an 
instanceof(TrainStop).


---Brett.


*********** REPLY SEPARATOR  ***********

On 3/2/2005 at 7:37 PM Erik Vos using eri...@hc... declared:

>The pedantic version could be
>              
>            / TokenableRevenuePoint
>RevenuePoint
>            \ NonTokenableRevenuePoint
>
>but perhaps better
>
>    / City 
>Stop 
>    \ Town
>

********** REPLY SEPARATOR END **********
This message sent with 100% recycled electrons.