'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 :)
>>
>
> I sincerely hope that this was an ironic statement. The complete lack of
> error
> handling in the EFL (well, apart from image loading) is dooming like the
> sword of damocles. I'm afraid as EFL gets more popular this will be a _major_
> hindrance for professional adoption and I'd really like us to revisit this
> before it's too late (read: stable APIs).
>
>
That's not entirely accurate. There's quite a bit of error
checking in many of the efl, though there could certainly be much
more. But there's little or no error-reporting (even the image
loading stuff isn't actually correctly enabled.. at least it wasn't
some time back, haven't checked recently).
In evas for example, most things will simply fail "silently"
in that a default state is used (eg. if image loading fails, an
opaque white image is used). Whether further error-reporting, or
at least some return state of fail/success is desirable...
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
