kimcinoo
/
efl
forked from enlightenment/efl
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
efl/src/tests/eolian/data/class_simple_ref.c

46 lines
1.6 KiB
C
Raw Normal View History

Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
Eina_Bool _class_simple_a_set(Eo *obj, Evas_Simple_Data *pd, int value);
evas: Rename Evas.Object to Efl.Canvas.Object One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-20 21:26:15 -07:00
EOAPI EO_FUNC_BODYV(efl_canvas_object_simple_a_set, Eina_Bool, EINA_TRUE, EO_FUNC_CALL(value), int value);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
int _class_simple_a_get(Eo *obj, Evas_Simple_Data *pd);
evas: Rename Evas.Object to Efl.Canvas.Object One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-20 21:26:15 -07:00
EOAPI EO_FUNC_BODY_CONST(efl_canvas_object_simple_a_get, int, 100);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
void _class_simple_b_set(Eo *obj, Evas_Simple_Data *pd);
evas: Rename Evas.Object to Efl.Canvas.Object One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-20 21:26:15 -07:00
EOAPI EO_VOID_FUNC_BODY(efl_canvas_object_simple_b_set);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
eolian: add a new references system to help replace pointers It's now possible to mark struct fields and function params as "references", which causes them to become pointers in C (in bindings, they become whatever is necessary). They're not a part of the type and are much more restricted than pointers, allowing bindings to be easier. This system will be gradually utilized and expanded as required. @feature
2016-06-06 07:22:56 -07:00
char * _class_simple_foo(Eo *obj, Evas_Simple_Data *pd, int a, char *b, double *c, int *d);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
eolian: add a new references system to help replace pointers It's now possible to mark struct fields and function params as "references", which causes them to become pointers in C (in bindings, they become whatever is necessary). They're not a part of the type and are much more restricted than pointers, allowing bindings to be easier. This system will be gradually utilized and expanded as required. @feature
2016-06-06 07:22:56 -07:00
static char * __eolian_class_simple_foo(Eo *obj, Evas_Simple_Data *pd, int a, char *b, double *c, int *d)
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
{
Eolian/Generator: support @empty and @auto. Local and base class functions are supported. When @empty is provided, dummy functions (initializing the parameters with default values if needed) are generated. When @auto is provided on properties, access to internal data variables is done. On set, it will assign parameters values to private data members. On get, parameters are set with private data members values. See the supplied tests as examples. @feature
2014-09-04 03:22:31 -07:00
if (c) *c = 1337.600000;
eolian: add a new references system to help replace pointers It's now possible to mark struct fields and function params as "references", which causes them to become pointers in C (in bindings, they become whatever is necessary). They're not a part of the type and are much more restricted than pointers, allowing bindings to be easier. This system will be gradually utilized and expanded as required. @feature
2016-06-06 07:22:56 -07:00
return _class_simple_foo(obj, pd, a, b, c, d);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
}
evas: Rename Evas.Object to Efl.Canvas.Object One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-20 21:26:15 -07:00
EOAPI EO_FUNC_BODYV(efl_canvas_object_simple_foo, char *, NULL, EO_FUNC_CALL(a, b, c, d), int a, char *b, double *c, int *d);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
eolian: support @ref on returns This adds basic support for @ref on return types.
2016-06-07 06:59:36 -07:00
int * _class_simple_bar(Eo *obj, Evas_Simple_Data *pd, int x);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
evas: Rename Evas.Object to Efl.Canvas.Object One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-20 21:26:15 -07:00
EOAPI EO_FUNC_BODYV(efl_canvas_object_simple_bar, int *, 0, EO_FUNC_CALL(x), int x);
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
Change the EFL to follow the new Eo rename.
2016-08-10 07:23:04 -07:00
static const Efl_Op_Description _class_simple_op_desc[] = {
evas: Rename Evas.Object to Efl.Canvas.Object One step closer to make the EO inheritance tree look like it's all Efl.
2016-06-20 21:26:15 -07:00
EO_OP_FUNC(efl_canvas_object_simple_a_set, _class_simple_a_set),
EO_OP_FUNC(efl_canvas_object_simple_a_get, _class_simple_a_get),
EO_OP_FUNC(efl_canvas_object_simple_foo, __eolian_class_simple_foo),
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
};
Change the EFL to follow the new Eo rename.
2016-08-10 07:23:04 -07:00
static const Efl_Class_Description _class_simple_class_desc = {
Eolian/Generator: support params initialization. This is needed when get properties or methods have to return a value in case of failure or to initialize parameters. The way used is to generate an intermediate function that will initialize the parameters and then invoke the "user" function.
2014-09-02 07:00:14 -07:00
EO_VERSION,
"Class_Simple",
EO_CLASS_TYPE_REGULAR,
EO_CLASS_DESCRIPTION_OPS(_class_simple_op_desc),
NULL,
sizeof(Evas_Simple_Data),
NULL,
NULL
};
Eo: reduce memory usage across applications. As described by Carsten in his email to edev ML titled: "[E-devel] eo stability - i think we need to postpone that" with the switch to Eo2 we significantly increased our usage of RW memory pages, and thus significantly increased our memory usage when running multiple applications. The problem was that during the migration to Eo2 the op id cache and the op description arrays were merged, causing the op description arrays to no longer be RO. This patch enables users of Eo (mainly Eolian) to declare those arrays as const (RO) again, saving that memory. There might be performance implications with this patch. I had to remove the op desc array sorting, and I used a hash table for the lookup. I think the op desc sorting doesn't really affect performance because that array is seldom accessed and is usually pretty short. The hash table is not a problem either, because it's behind the scenes, so it can be changed to a more efficient data structure if the hash table is not good enough. The hash table itself is also rarely accessed, so it's mostly about memory. Please keep an eye for any bugs, performance or excessive memory usage. I believe this should be better on all fronts. This commit *BREAKS ABI*. @fix
2015-09-28 09:18:43 -07:00
EO_DEFINE_CLASS(class_simple_class_get, &_class_simple_class_desc, NULL, NULL);