On 2012.09.17 06:52, Peter Stuge wrote:
> I agree where one knows what one doesn't know, but it's likely to
> cause problems where one doesn't know what one doesn't know.
Care to be more cryptic? Are trying to say that I should have
anticipated the issue mentioned by the OP. Because if you do, th
Pete Batard wrote:
> > I don't understand why the fd integer is allocated using _open()
> > instead of allocating it in the library using a simple counter or so.
>
> Because "using a simple counter or so" requires more lines of codes to
> ensure we are emulating fd allocation than a one line call
On 2012.09.16 12:59, Peter Stuge wrote:
> Pete Batard wrote:
>> the error basically comes
>> from trying the following: _open("NUL", _O_WRONLY);
>
> I don't understand why the fd integer is allocated using _open()
> instead of allocating it in the library using a simple counter or so.
Because "usi
Pete Batard wrote:
> the error basically comes
> from trying the following: _open("NUL", _O_WRONLY);
I don't understand why the fd integer is allocated using _open()
instead of allocating it in the library using a simple counter or so.
It seems that the fd is just a placeholder; no actual IO goe
On 2012.08.17 15:04, 13456 1653 wrote:
>
> Hello, i want to init libusb on the Windows Embedded Standart SP3
From this [1], I'll assume that your target CPU is x86 compatible, right?
> but it crashed.
Not entirely surprising, since this is an environment that we have never
tested, due to (as f
