On Thursday, May 13, 2010, at 05:04PM, "Tom Browder" <tom.brow...@gmail.com>
wrote:
>On Thu, May 13, 2010 at 15:16, Christopher Sean Morrison <brl...@mac.com>
>wrote:
>...
>> That said, 'aircode' is one of those non-geometric properties that would be
>> nice to get rid of (i.e., let applications set their ...
>> Line of sight equivalence is another one that would be good to get rid of or
>> -- even better -- generalized, but it shouldn't
>
>All very well, but how do you plan to handle city hall where those are
>embedded in lots of legacy code?
By having and following clear deprecation rules for making old code obsolete,
so developers know what to expect when it happens. Nothing is going to prevent
them from using the versions their using, it would only be to update to the
latest to get future benefits.
That said, for old items like los and air, compatibility interfaces could be
put in place so the impacts are minimized or even completely masked. If they
were to be removed (made obsolete), it certainly wouldn't be until a major
revision change (e.g., BRL-CAD 8.0) anyways where all bets are off in terms of
compatibility. Major revision changes are explicitly defined as being
backwards incompatible.
We've been slowly accumulating a list of changes for release 8 in the TODO file
for features that can't be implemented without breaking compatibility. There's
a rel8 branch in SVN for working on those features.
Cheers!
Sean
------------------------------------------------------------------------------
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
