Hi Will,
* [18.04.08 00:10]:
The first time I loaded this module, E segfaulted. It loaded successfully
the next time, though. However,
since unloading it I am unable to load the module again - E segfaults on
every attempt. I am attaching a
backtrace from gdb.
Did you load this module
All ELFs are written in this way, without error checking and reporting, i
think it's for performance reason and I like it :)
We can simply modify the function to return 1 on success or 0 on error
*poker face*
I see you rational, well measured idea and raise you a loony wiki article:
On Fri, Apr 18, 2008 at 2:05 PM, andres [EMAIL PROTECTED] wrote:
All ELFs are written in this way, without error checking and reporting, i
think it's for performance reason and I like it :)
We can simply modify the function to return 1 on success or 0 on error
*poker face*
I see you
Michael Stapelberg wrote:
Hi Will,
* [18.04.08 00:10]:
The first time I loaded this module, E segfaulted. It loaded successfully the next time, though. However,
since unloading it I am unable to load the module again - E segfaults on every attempt. I am attaching a
backtrace from gdb.
- Will Keaney [EMAIL PROTECTED] ha scritto:
Michael Stapelberg wrote:
Hi Will,
* [18.04.08 00:10]:
The first time I loaded this module, E segfaulted. It loaded
successfully the next time, though. However,
since unloading it I am unable to load the module again - E
Build log for Enlightenment DR 0.17 on 2008-04-18 07:09:21 -0700
Build logs are available at http://download.enlightenment.org/tests/logs
Packages that failed to build:
ecore_li http://download.enlightenment.org/tests/logs/ecore_li.log
engage
This is the kind of thing that makes 'chaining' of arbitrary
filters a problem unless very strict semantic rules are followed,
and an api used which is able to naturally represent those rules.
I'll continue this a bit later, but please do jump in
with comments or whatnot if
We could put checks like this in edje_object_part_swallow. But I can't
help to
think was programmed to work this way for a reason I ignore.
All ELFs are written in this way, without error checking and reporting, i
think it's for performance reason and I like it :)
I sincerely hope that
EAPI unsigned char ***
edje_object_part_swallow(Evas_Object *obj, const char *part, Evas_Object
*obj_swallow) {
Edje *ed;
Edje_Real_Part *rp;
ed = _edje_fetch(obj);
if ((!ed) || (!part)) return 0; *
rp = _edje_real_part_recursive_get(ed, (char *)part);
if
andres wrote:
EAPI unsigned char ***
edje_object_part_swallow(Evas_Object *obj, const char *part, Evas_Object
*obj_swallow) {
Edje *ed;
Edje_Real_Part *rp;
ed = _edje_fetch(obj);
if ((!ed) || (!part)) return 0; *
rp = _edje_real_part_recursive_get(ed, (char
'Mickey' wrote:
We could put checks like this in edje_object_part_swallow. But I can't
help to
think was programmed to work this way for a reason I ignore.
All ELFs are written in this way, without error checking and reporting, i
think it's for performance reason and I like it :)
11 matches
Mail list logo
