On Fri, Sep 07, 2007 at 06:52:21PM +0200, Tóth István wrote:
Hello!
I am currently working on java bindings for libvirt, and in the process
Interesting, so you're using JNI direct access to the C library, right ?
I looked at this a few weeks ago, but it was looking like accessing using the
Tóth István wrote:
I believe that the fields of these structs ARE meant to be read by the
applications linking the library, and are not really meant to be
opaque. (or if they are, they should have some functions/macros that you
can access their contents with)
Yes, you should access the fields
Thanks for the replays
If an individual stats field isn't supported by the hypervisor, it
will be returned as ((long long) -1) [for various reasons we're using
long long here, but really we mean 64 bit signed int].
Thats very useful info, I spent quite a lot of time messing with
BigIntegers,
Tóth István wrote:
Thanks for the replays
If an individual stats field isn't supported by the hypervisor, it
will be returned as ((long long) -1) [for various reasons we're using
long long here, but really we mean 64 bit signed int].
Thats very useful info, I spent quite a lot of time messing
Hello!
I am currently working on java bindings for libvirt, and in the process
I have found a few bugs with the documentation, and also what I believe
to be a design problem in the API.
1. The parameterized C macros do not have their arguments listed either
on libvirt.org, or in the docs folder
Hello!
I am currently working on java bindings for libvirt, and in the process
I have found a few bugs with the documentation, and also what I believe
to be a design problem in the API.
1. The parameterized C macros do not have their arguments listed either
on libvirt.org, or in the docs
On Fri, Sep 07, 2007 at 06:52:21PM +0200, T?th Istv?n wrote:
Hello!
I am currently working on java bindings for libvirt, and in the process
I have found a few bugs with the documentation, and also what I believe
to be a design problem in the API.
1. The parameterized C macros do not have
