Re: [Gambas-devel] gb.api
Brought to you by:
gambas
From: fabien <gam...@wa...> - 2005-04-25 19:06:12
|
Hi benoit Is it for the 1.9.7 ? In fact i use the Daniel component currently to test the opengl libs. It's really interesting... but i think something interesting will be to be able to add some widget not included in the current or the common component. Like i was doing on windows in the past. With the coolbar or treeview to replace the ocx one (activex) it take less space in memory. Regards, Fabien Bodard > Hi, Daniel. > > Good job, but you should have tell before that you were working on that. > Because I'm currently adding this feature directly inside the interpreter. > > Declaring a method would be something like that: > > [PUBLIC] EXTERN Func(Param1 AS Type1, Param2 AS Type2, ...) As ReturnType > IN "Library" WITH "C function prototype" > > This is equivalent to your Api.Register method. The C function prototype is > a string that will be transformed by the compiler into a static description > of the C function. > > The function will be called like a normal function. > > This is equivalent to your ApiCall.* method. > > I wanted to add a "Struct" class to manage C structure in memory, but with > special syntax support from the compiler. > > This is equivalent to your ApiPointer class I think. > > I'm not sure that your implementation of ApiCall._unknown is very > portable... I think it works on i386, 32 bits ;-) Well, like Gambas one > could say ;-) > > I'm not sure the way you call functions work everywhere. Is is sure that > passing a structure by value is equivalent to pass the arguments one by one > ? That the order of arguments will be preserved on another architecture ? > > Maybe I should add the same memory & string utility functions you added to > the component. > > Support for callbacks may be interesting too... > > What do you think about that ? |