aerofiles.xcsoar.ObservationZone object about aerofiles HOT 1 CLOSED

You are proposing to use objects as parameters to methods instead of individual values. I completely agree, that this is a better way to structure aerofiles. However, aerofiles currently uses values and not objects for all their methods. So I dont see a good reason, why we should only change ObservationZone to OO and keep all other methods handling values.

So either we go completely OO or nowhere, otherwise we have two different types of parameter passing, which leads to irritation.

Going completely to OO would be a big change. It would be either duplication of code (as you propose) or incompatible (if we drop parameter values).

So I would currently not follow your proposed change, for the above reasons. Did I oversee something?

from aerofiles.