[Octave-bug-tracker] [bug #45659] version function: options and return values supported by Matlab

[Markus Mützel]

Follow-up Comment #15, bug #45659 (project octave):

In this version of the patch, the release date and the build date and time are
part of the ___octave_config_info___ struct.

Now build-info.cc is the file that is generated by the script and the header
is static like you suggested. I agree that this is a much better approach.

Regarding the version functions defined in each library: Would these be
versions that only change once in a while (hence not the hg id)? Would these
be the same as OCTAVE_VERSION?

With this patch version.m supports all documented flags.
Is it OK to use the try catch statement for the Java functions? Is it reliable
to check __octave_config_info__.build_features.JAVA instead?

I don't know how to get the info requested in comment #0. Does anyone have an
idea how to check the vendor and version of the linked in BLAS and LAPACK
libraries? 

The current output of version.m and the new fields of ___octave_config_info___
with this patch on my system are:

>> version
ans = 4.1.0+
>> [v,d]=version
v = 4.1.0+
d = 2015-05-26
>> version ("-date")
ans = 2015-05-26
>> version ("-description")
ans =
>> version ("-release")
ans =
>> version ("-java")
ans = Java 1.8.0_66-internal-b17 with Oracle Corporation OpenJDK 64-Bit Server
VM mixed mode
>> version ("-blas")
warning: version: option '-blas' not implemented
warning: called from
    version at line 93 column 9
ans =
>> version ("-lapack")
warning: version: option '-lapack' not implemented
warning: called from
    version at line 96 column 9
ans =
>> __octave_config_info__.hgid
ans = e3888aa9a4d1+
>> __octave_config_info__.releasedate
ans = 2015-05-26
>> __octave_config_info__.builddate
ans = Apr  8 2016
>> __octave_config_info__.buildtime
ans = 20:37:04



(file #36869)
    _______________________________________________________

Additional Item Attachment:

File name: version_beta3.patch            Size:11 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45659>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/