Re: [Libusb-devel] Understanding libusb_transfer.iso_packet_desc

[Daniel D. <ds...@ge...>]

Tim is exactly right from a theoretical standpoint but I just want to 
point out in this specific example:

Tim Roberts wrote:
> except that with [0], sizeof works properly.  So, for example, you can say:
> 
>     struct libusb_transfer * ttt = (struct libusb *) malloc(
> sizeof(struct libusb_transfer) + 10 * sizeof(struct
> libusb_iso_packet_descriptor) );

It is not legal to malloc your own transfers with libusb. You must use 
the libusb allocation/freeing functions.

(But yes, this is effectively how it works - the [0] allows the struct 
to exist with whatever size is needed for the isochronous packets.)

Daniel