[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
When to bump library api version (current)
From: |
Adam Mercer |
Subject: |
When to bump library api version (current) |
Date: |
Wed, 19 May 2010 23:09:06 -0500 |
Hi
We are coming up for a new release of one of the libraries I maintain
and I'm not sure whether the library api version needs bumping
(specifically current). The only API change is that the function
below:
double calculate_ligo_snr_from_strain(
REAL4TimeVectorSeries *strain,
SimInspiralTable *thisInj,
char ifo[3]);
has changed to:
double calculate_ligo_snr_from_strain(
REAL4TimeVectorSeries *strain,
SimInspiralTable *thisInj,
const char ifo[3]);
i.e. the third argument has changed from char to const char, whilst
this is technically an API change I'm not sure if it warrants an API
bump? Should current be bumped in this case or is it OK not to bump
current (or bump both current and age)?
Cheers
Adam
- When to bump library api version (current),
Adam Mercer <=