On 15 Feb, 13:53, "MIG" wrote:
Given that programming it one way must be as easy as programming it
the other way, my question was about the justification for programming
it to treat it as an unresolved journey when everything about it was
totally resolved.

I don't know. The Oyster Card has very limited data storage, so I'd
imagine programming for it isn't fun, especially considering the
number of features and routes and rules that have to be accounted for.
My guess is they were working around some other bug and due to the
limitations of the system couldn't have it both ways.

U

wrote:
On 15 Feb, 13:53, "MIG" wrote:
Given that programming it one way must be as easy as programming it
the other way, my question was about the justification for programming
it to treat it as an unresolved journey when everything about it was
totally resolved.

I don't know. The Oyster Card has very limited data storage, so I'd
imagine programming for it isn't fun, especially considering the
number of features and routes and rules that have to be accounted for.
My guess is they were working around some other bug and due to the
limitations of the system couldn't have it both ways.

My guess would be they didn't think about this corner case really.
--
Michael Hoffman