[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why no more OCTAVE_API_VERSION_NUMBER?
From: |
Orion Poplawski |
Subject: |
Why no more OCTAVE_API_VERSION_NUMBER? |
Date: |
Mon, 30 Dec 2013 13:41:27 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
This commit:
changeset: 17510:7542f4496974
user: John W. Eaton <address@hidden>
date: Sat Sep 28 15:04:14 2013 -0400
summary: eliminate some macros in version.h
Appears to have gotten rid of OCTAVE_API_VERSION_NUMBER from version.h. It
appears that at least swig uses this macro in #ifdefs to handle changes in the
Octave api and this is breaking swig generated code for octave 3.8.0 (see
https://sourceforge.net/p/swig/bugs/1353/).
Is there a particular reason for this change? Is there a better way to check
API versions? The text string OCTAVE_API_VERSION is a lot harder to parse.
Thanks,
Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane address@hidden
Boulder, CO 80301 http://www.nwra.com
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Why no more OCTAVE_API_VERSION_NUMBER?,
Orion Poplawski <=