On Tue, 08 May 2012 10:52:21 +0300 Tom Hacohen said:
> On 08/05/12 10:41, Vincent Torri wrote:
> > http://eodev.sourceforge.net/eo/doc/html/index.html
> >
> > it's a C++ library that has eo as namespace. That means that if
> > someone writes a C++ binding of our Eo, its namespace will conflict
>
On 08/05/12 10:41, Vincent Torri wrote:
> http://eodev.sourceforge.net/eo/doc/html/index.html
>
> it's a C++ library that has eo as namespace. That means that if
> someone writes a C++ binding of our Eo, its namespace will conflict
> withthe above library if they are used together.
Again, good poi
On Tue, May 08, 2012, Vincent Torri wrote:
> On Tue, May 8, 2012 at 9:27 AM, Tom Hacohen wrote:
> > On 08/05/12 10:25, Vincent Torri wrote:
> >>
> >> I also don't know such lib, but i also don't know the libraries that
> >> will be written in the future as well.
> >
> >
> > That's their job not to
On Tue, May 8, 2012 at 9:27 AM, Tom Hacohen wrote:
> On 08/05/12 10:25, Vincent Torri wrote:
>>
>> I also don't know such lib, but i also don't know the libraries that
>> will be written in the future as well.
>
>
> That's their job not to steal the namespace, the same way we hope they won't
> ste
On 08/05/12 10:25, Vincent Torri wrote:
> I also don't know such lib, but i also don't know the libraries that
> will be written in the future as well.
That's their job not to steal the namespace, the same way we hope they
won't steal azy, evas, eina and etc...
--
Tom.
-
On Tue, May 8, 2012 at 9:20 AM, Tom Hacohen wrote:
> On 08/05/12 10:09, Vincent Torri wrote:
>>
>> I'm just wondering : isn't 'eo' too small for the namespace ? I would
>> really prefer 'eobj'. It's not that big and might avoid conflicts with
>> other libraries which would also choose 'eo' as name
On 08/05/12 10:09, Vincent Torri wrote:
> I'm just wondering : isn't 'eo' too small for the namespace ? I would
> really prefer 'eobj'. It's not that big and might avoid conflicts with
> other libraries which would also choose 'eo' as namespace
I don't know of any other libraries that use eo for t
I'm just wondering : isn't 'eo' too small for the namespace ? I would
really prefer 'eobj'. It's not that big and might avoid conflicts with
other libraries which would also choose 'eo' as namespace
Vincent
On Tue, May 8, 2012 at 8:56 AM, Enlightenment SVN
wrote:
> Log:
> Eo: Make eo_parent_get
On 23/04/12 15:34, Vincent Torri wrote:
> hmm, why do you need to return it in wref, then ???
I don't understand what you mean. I'm setting wref to obj and
registering wref as a pointer that'll be updated automatically upon
deletion of the object... I didn't update the docs yet (doing it atm),
On Mon, Apr 23, 2012 at 2:32 PM, Enlightenment SVN
wrote:
> Log:
> Eobj: Make eobj_weak_ref_add return the obejct being reffed.
>
> Suggested by vtorri.
>
> Author: tasn
> Date: 2012-04-23 05:32:36 -0700 (Mon, 23 Apr 2012)
> New Revision: 70418
> Trac: http://trac.enlightenm
Hehe, yeah. :) The other Daniel, not you ;)
--
Tom.
On 18/04/12 13:23, Daniel Juyung Seo wrote:
> hehe obviously there are multiple instances of daniel now.
> On Apr 17, 2012 9:58 PM, "Enlightenment SVN"
> wrote:
>
>> Log:
>> Eobj: Fixed docs.
>>
>> Thanks to Daniel.
>>
>> Author: tasn
>>
hehe obviously there are multiple instances of daniel now.
On Apr 17, 2012 9:58 PM, "Enlightenment SVN"
wrote:
> Log:
> Eobj: Fixed docs.
>
> Thanks to Daniel.
>
> Author: tasn
> Date: 2012-04-17 05:58:33 -0700 (Tue, 17 Apr 2012)
> New Revision: 70268
> Trac: http://trac.en
12 matches
Mail list logo
