Re: [Silgraphite-devel] Fwd: API for version number?

[Sharon C. <sha...@si...>]

Okay, I'm finally doing this. Any objection to calling the method 
"EngineVersion"? There are just so many different version numbers 
floating around (compiler, various tables, etc), that "GraphiteVersion" 
seems ambiguous to me!

It's a static method on the Segment class, so the call will look 
something like:

        int nMajorVersion, nMinorVersion, nBugFixVersion;
        gr::Segment::EngineVersion(&nMajorVersion, &nMinorVersion, 
&nBugFixVersion);


Jonathan Kew wrote:
> On 20 Apr 2010, at 14:17, Martin Hosken wrote:
>
>   
>> Dear Jonathan,
>>
>>     
>>> Could we please have version number APIs, as requested some time ago  
>>> (see below)? Ideally, both compile-time version (preprocessor symbols  
>>> such as GRAPHITE_VERSION) and an API so that the app can determine at  
>>> runtime what version of Graphite it is linked with. (When using  
>>> dynamic libraries, this might not be the same as the version it was  
>>> built with.)
>>>       
>> Sorry to be so slow on this. We are considering a new release which will be 2.4.0 and have a bumped library version. What functions would you like to see us add to report the information you want?
>>     
>
> I'd probably go for some compile-time #defines that end up in a public header, such as
>
>   #define  GRAPHITE_VERSION_MAJOR   2
>   #define  GRAPHITE_VERSION_MINOR   4
>   #define  GRAPHITE_VERSION_BUGFIX  0
>
> and a library function that returns these at runtime, e.g,
>
>   void gr::GraphiteVersion(int* major, int* minor, int* bugfix);
>
> (I don't remember what your naming conventions are like, or whether you use "int" in public APIs.... adjust as appropriate.)
>
> That makes it easy for client code to report "Built with Graphite version 2.4.0; using library version 2.4.3" or whatever.
>
> Thanks,
>
> JK
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Silgraphite-devel mailing list
> Sil...@li...
> https://lists.sourceforge.net/lists/listinfo/silgraphite-devel
>
>