yang686526

error in oda: svcs.versionstring()
error in oda: svcs.versionstring()
hi,
the function 'svcs.versionstring()' is buggy and always returns the version "2.02" in the past 4 or 5 dd versions including the banned version r2.10.
how we would comply to the court order and to oda recommendation that we cease using version 2.1.0 if old programs we created and distrubuted to the end users display always version 2.02.
can someone solves this puzzle and also fix the bug for us.
thanks,
salleh diab
attached images
current version is 2.02.0
the banned version is 2.1.0 (=2.01.0)
vladimir
i checked 2.1 samples and they print correct message with version 2.01.....
sergey slezkin
ok taking your own words:
the banned version dd v2.10 displays: version 2.01
and your new legal version after the court order dd v2.11 dispalys also: version 2.01.
as seen in the two attached images.
is that a puzzle or what? if i ask my clients to send to me the oda version displayed on the log file, how do i know if it is legal or not?
i just digged a little bit deeper and also found a sub-version! should this be a robust part of the 'svcs.versionstring'?
sydiab
attached images (8.2 kb, 8 views)
(8.2 kb, 7 views)

last edited by sydiab; 18th december 2006 at 04:40 pmfff">.
versionstring() returns major_version.minor_version
2.1.0 and 2.1.1 are binary compatible and have the same major an minor versions. they differ only in "major_build" number. dd_major_build_version (and other version related symbols) is defined in ddversion.h. you may format it as you wish.
if you are using dlls, you may ask your clients to look at the dd dlls properties. there is listed all the version information.
if you are using libs, all you may depend upon, is you own product version.
vladimir
many thanks, vladimir.