Em 09-09-2015 06:03, Mark Rotteveel escreveu:
>>
>> BTW, I wonder, how could the Jaybird JNA interpret (read numbers and
>> strings) status vectors? Or just it could not, always leaving the job
>> for fb_interpret?
>
> JNA can use pointers, and Jaybird does (with the old API). I don't use
> fb_i
On 9-9-2015 11:11, Alex Peshkoff wrote:
> On 09/09/2015 12:03 PM, Mark Rotteveel wrote:
>> On 7-9-2015 16:39, Adriano dos Santos Fernandes wrote:
>>> Hi!
>>>
>>> Idea behind cloop is to have descriptive idl file so that bindings for
>>> different types of languages would be generated automatically.
On 09/09/2015 12:03 PM, Mark Rotteveel wrote:
> On 7-9-2015 16:39, Adriano dos Santos Fernandes wrote:
>> Hi!
>>
>> Idea behind cloop is to have descriptive idl file so that bindings for
>> different types of languages would be generated automatically.
>>
>> Currently the idl grammar is simple and
On 7-9-2015 16:39, Adriano dos Santos Fernandes wrote:
> Hi!
>
> Idea behind cloop is to have descriptive idl file so that bindings for
> different types of languages would be generated automatically.
>
> Currently the idl grammar is simple and effective for C, C++ and Pascal.
>
> But we use intptr
On 09/07/2015 05:39 PM, Adriano dos Santos Fernandes wrote:
> Hi!
>
> Idea behind cloop is to have descriptive idl file so that bindings for
> different types of languages would be generated automatically.
>
> Currently the idl grammar is simple and effective for C, C++ and Pascal.
>
> But we use i
Hi!
Idea behind cloop is to have descriptive idl file so that bindings for
different types of languages would be generated automatically.
Currently the idl grammar is simple and effective for C, C++ and Pascal.
But we use intptr type for errors codes or strings.
No matter how we improve the clo
