Csound Csound-dev Csound-tekno Search About

[Csnd-dev] API: version, subversion, patch

Date2024-10-08 13:57
FromSteven Yi
Subject[Csnd-dev] API: version, subversion, patch
Hi All,

One thing I thought though was we have the strange csoundGetVersion in the API which returns version number multiplied by 1000. That's pretty odd. ;) I was thinking we should have 

csoundGetVersion()
csoundGetSubversion()
csoundGetPatch()

or 

csoundGetVersionString()

with the latter returning ${version}.${subVersion}.${patch}

Or both?  The first set of functions could be useful for plugins or hosts which might require that level of granularity (i.e., new feature was added in 7.05, so my plugin requires at least that...). I think version string would be useful for some apps for simple display of the version and it's easily parseable, but I suppose easy enough to create by the developer using the first set of functions. 

Thoughts?

steven 

Date2024-10-08 14:59
Fromvlz
SubjectRe: [Csnd-dev] API: version, subversion, patch
I think it is a good idea. The current API function is actually a bit odd.

Prof. Victor Lazzarini
Maynooth University
Ireland

> On 8 Oct 2024, at 13:58, Steven Yi  wrote:
> 
> 
> Hi All,
> 
> One thing I thought though was we have the strange csoundGetVersion in the API which returns version number multiplied by 1000. That's pretty odd. ;) I was thinking we should have 
> 
> csoundGetVersion()
> csoundGetSubversion()
> csoundGetPatch()
> 
> or 
> 
> csoundGetVersionString()
> 
> with the latter returning ${version}.${subVersion}.${patch}
> 
> Or both?  The first set of functions could be useful for plugins or hosts which might require that level of granularity (i.e., new feature was added in 7.05, so my plugin requires at least that...). I think version string would be useful for some apps for simple display of the version and it's easily parseable, but I suppose easy enough to create by the developer using the first set of functions. 
> 
> Thoughts?
> 
> steven