Re: [E-devel] About ecore_pipe_add/del pair

[Gustavo S. B. <bar...@pr...>]

On Wed, May 23, 2012 at 7:49 AM, Carsten Haitzler <ra...@ra...> wrote:
> On Mon, 7 May 2012 19:09:45 +0900 (KST) Jiyoun Park <jij...@na...> said:
>
> hmm realistically ecore_init and shutdown (same really with almost any efl api)
> is intended to be run ONCE per process and the shutdown once at process
> termination. not multiple times. it's a lot harder to make this always work in
> the repeated init/shutdown case and frankly was never intended for this or
> tested and implemented for it. my suggestion: only init once and shut down
> once. :)

I know you wrote this based on an application writer point of view.
But given this is a generic mail list, please make the following
remark visible:

 - always init and shutdown ONCE per your CALL SITE usage.

That means: if you write an app that uses ecore_* symbols, always call
ecore_init() and ecore_shutdown() from your app. Even if you get that
ecore_* from elementary_init()[1]. This consistency will save you
headaches in the future. And this rule easily applies to library,
being consistent everywhere. Actually it is the case to solve DSO
problems in linkage, pkg-config problems and so on.

[1] I know many of us don't do ecore_init(), evas_init(),
eina_init()... and so on when using elementary_init(). Saves typing,
but is bad for consistency. If you explicitly use these symbols, as we
often do, then it's better to explicitly call them and avoid issues.
If you're experienced enough to skip them, do it but do not RECOMMEND
it to people :-)  [if you don't call any ecore_evas_*, then there is
no need to ecore_evas_init()...]

-- 
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: bar...@gm...
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202