Hi,
On Thu, Sep 23, 2021 at 03:24:22PM +0100, Daniel P. Berrangé wrote:
> On Thu, Sep 23, 2021 at 04:07:17PM +0200, Victor Toso wrote:
> > Hi,
> >
> > On Thu, Sep 23, 2021 at 11:47:58AM +0100, Daniel P. Berrangé wrote:
> > > In order to auto-generate more of the language binding code, it is
> >
On Thu, Sep 23, 2021 at 04:07:17PM +0200, Victor Toso wrote:
> Hi,
>
> On Thu, Sep 23, 2021 at 11:47:58AM +0100, Daniel P. Berrangé wrote:
> > In order to auto-generate more of the language binding code, it is
> > desirable to know what libvirt version an API was introduced in.
> > We can extract
Hi,
On Thu, Sep 23, 2021 at 11:47:58AM +0100, Daniel P. Berrangé wrote:
> In order to auto-generate more of the language binding code, it is
> desirable to know what libvirt version an API was introduced in.
> We can extract this information from the .syms files and expose
> it in the API
On 9/23/21 12:47 PM, Daniel P. Berrangé wrote:
> In order to auto-generate more of the language binding code, it is
> desirable to know what libvirt version an API was introduced in.
> We can extract this information from the .syms files and expose
> it in the API description
>
> eg instead of
>
In order to auto-generate more of the language binding code, it is
desirable to know what libvirt version an API was introduced in.
We can extract this information from the .syms files and expose
it in the API description
eg instead of
we now have
This will benefit this proposal:
