Hi,
I would like to know whether there is any way to indicate the next
GNUstep release for GS_API_VERSION macro.
For example, when you add a new method, it will be available only
with the next release, but at the time you commit header/
implementation update related you cannot know for sure
Hi Quentin,
I may not understand your problem correctly, but if you only want to
make sure that the new functionality is available and you know that it
was not available at a certain release version of GNUstep, but will be
in what ever version comes next. Then it should be possible to just use
the
On 9 Aug 2006, at 11:14, Quentin Mathé wrote:
Hi,
I would like to know whether there is any way to indicate the next
GNUstep release for GS_API_VERSION macro.
For example, when you add a new method, it will be available only
with the next release, but at the time you commit header/
imple
On Aug 9, 2006, at 7:10 AM, Richard Frith-Macdonald wrote:
I understand the problem, but I don't think the best solution is to
add new macros and scripting. Rather, I think it's to adopt a
slightly more rigorous approach to making releases. What I propose is
this ...
When we make a release
Le 9 août 06 à 17:20, Adam Fedor a écrit :
On Aug 9, 2006, at 7:10 AM, Richard Frith-Macdonald wrote:
I understand the problem, but I don't think the best solution is
to add new macros and scripting. Rather, I think it's to adopt a
slightly more rigorous approach to making releases. What
Am 09.08.2006 um 12:14 schrieb Quentin Mathé:
For example, when you add a new method, it will be available only
with the next release, but at the time you commit header/
implementation update related you cannot know for sure what will be
the next version number of the library.
One solutio
