[Flightgear-devel] Local Weather - backward compatibility

[<tho...@jy...>]

> Please note, the check for
> features.can_disable_environment == 1 is gone now. It doesn't make any
> sense there.

In a current GIT, none of the checks make any sense, because current GIT
always has all the features. On the other hand, the purpose of the
compat_layer.nas is to provide compatibility of the weather to the last
stable release - so when 2.4 is out, I will remove all compatibility
checks, but as time goes on new ones will be added - which again allow you
to run later versions on 2.4, but give GIT users all the new shining
features.

I can't really maintain two separate versions for last stable and current
GIT - but I can maintain one version which works for both with the help of
the compat layer. I fear that it'd just gets a mess if you start removing
feature checks in the compat layer on GIT while I don't do it in my
version intended also for distribution through the Forums.

May I suggest to remove all the feature checks for the intended release
branch (if simply to get rid of the messages) and set all features to 1
there, but to leave the management of feature checks in the development
branch to me? I think that's least likely to create chaos.

Cheers,

* Thorsten