Hello

On 16/10/15 12:59, Tom Hacohen wrote:
> tasn pushed a commit to branch master.
>
> http://git.enlightenment.org/core/efl.git/commit/?id=8e2e7bd61e102e8e56dd6e2d605548c0856e2a88
>
> commit 8e2e7bd61e102e8e56dd6e2d605548c0856e2a88
> Author: Tom Hacohen <[email protected]>
> Date:   Fri Oct 16 11:42:37 2015 +0100
>
>      Eo events: Add a struct member marking if it's a legacy event or not.
>      
>      My previous patch to this piece of code
>      (37f84b7e966372384e2dfe5d191a6f907a17962e), caused a significant
>      performance regression. This is such a hot path, that even accessing the
>      strings when we don't have to slows things down drastically. It makes
>      more sense to just store it in the structure.
>      
>      This commit breaks ABI (though most people probably won't even need to
>      recompile anything else because of the memory layout).
>      It was discussed on IRC and was decided this is a big enough issue to
>      warrant a fix during the freeze.
>   

Is there still a plan to make EO stable with 1.16? Doing such changes 
only to two weeks away from the release in something as core as EO make 
me a bit nervous.

regards
Stefan Schmidt

------------------------------------------------------------------------------
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to