Re: [Rails-devel] Push request: Enforcement of forced train purchases

[Frederick W. <fre...@go...>]

Regarding the definition of routes:
Thanks for pointing out that there are variants that do not require
forcedly purchsed trains to run (at least 1844). Actually, I started
with a 2-train route check only to leave this approach when thinking
of hex trains. The patch could easily be amended to revert back to
that logic. (But, as Stefan said, the first step would consist of
clarify this in a discussion.)

Regarding rails' layering:
It would be a valid design decision to keep route awareness out of the
game engine. But then every consumer of the game engine has to take
care of becoming route aware on himself. Currently, that's not a big
deal as there is only one consumer (the UI). But in the longer term,
there could also be other consumers (RemoteHuman, AI) and, then,
having put route awareness into the game engine would come in very
handy.

Regarding incompatibility with Rails 2.0 (@Stefan):
Which aspect of this patch is incompatible to rails 2.0? Which
adjustment would be necessary in order to avert this?