On Sun, Feb 14, 2010 at 00:26, Christopher Sean Morrison <[email protected]> wrote:
> Minor API changes such as the one you encountered should be expected across

Sean, I'm not complaining about the API change (just was a little surprised).

> Version numbers were specifically hidden from headers to prevent developers
> from making compile-time affordances in code for multiple versions of API.

How does that hinder anyone who doesn't want to be hindered?

>  Exactly what it sounds like you're trying to do to work around the
> signature change.. :)  Those "#if version == whatever" compile-time checks
> are certainly convenient and simple but they slow down API evolution
> detrimentally and cause added migration burdens for all involved down the

Do you mean BRL-CAD developers?  If so, how would it bother them if
BRL-CAD itself didn't use the information?  Isn't providing a version
macro something that could be automated since you give each release a
version?

> Is this a case of looking for a technical solution to a sociological
> problem?  If you're collaborating with someone on a bit of code, it sounds
> like you both should be on the same version (at least the same minor
> version).  What is keeping your teammate from upgrading?  Or why are you

The problem is that the other part of the team is doing development
with Windows and they have had problems in the past with BRL-CAD on
Windows and are not as willing to update or install from source as us
*nix people are.

> doc/deprecation.txt).  If that was too much of a burden, I could always wrap
> the latest code in some arbitrary define that I pass as a CPPFLAG when I
> build.

That's what I've done, but it would be more convenient if there were a
version macro I could count on.

Thanks, Sean.

Regards,

-Tom

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to