Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-07 Thread ChunEon Park
t;; Cc: "enlightenment-devel"; Sent: 2012-10-03 (수) 23:16:14 Subject: Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas On 03/10/12 16:15, Michael Blumenkrantz wrote: > how? what errors? if you're deleting a null pointer, it's almost > certainly be

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
On 03/10/12 16:15, Michael Blumenkrantz wrote: > how? what errors? if you're deleting a null pointer, it's almost > certainly because you already nulled the input and thus are managing > your objects properly, which is what you're claiming people would be > missing with this behavior. It just mean

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Michael Blumenkrantz
On Wed, Oct 3, 2012 at 3:12 PM, Tom Hacohen wrote: > On 03/10/12 16:05, Michael Blumenkrantz wrote: > >> >> >> On Wed, Oct 3, 2012 at 3:01 PM, Tom Hacohen > > wrote: >> >> Hm.. ? In most cases you build a UI, use it, and then delete it at >> the hand, i.e m

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
On 03/10/12 16:05, Michael Blumenkrantz wrote: > > > On Wed, Oct 3, 2012 at 3:01 PM, Tom Hacohen > wrote: > > Hm.. ? In most cases you build a UI, use it, and then delete it at > the hand, i.e manage the UI properly. If the state in your > application re

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Michael Blumenkrantz
On Wed, Oct 3, 2012 at 3:01 PM, Tom Hacohen wrote: > Hm.. ? In most cases you build a UI, use it, and then delete it at the > hand, i.e manage the UI properly. If the state in your application requires > for an object to be deleted, it's deleted. Having an object pointer that > may point to some

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
Hm.. ? In most cases you build a UI, use it, and then delete it at the hand, i.e manage the UI properly. If the state in your application requires for an object to be deleted, it's deleted. Having an object pointer that may point to some random object that may be deleted is not the common case.

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
No, that's not following my logic. We need to make the common case super awesome, and the less common case awesome, and I think the common case is not deleting NULL objects, but just managing them properly. Therefore lets make the common case (NULL deletion is unwanted) super awesome and the le

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
I know what evas_objec_free() does, and it is not like free, even if the object is actually freed, because there's a graphical representation to the object, and it's an object on screen (in most cases). So just having a pointer that may be NULL and deleting it just in case is way less common th

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
I said it's *not* like the free case... On 03/10/12 14:05, Michael Blumenkrantz wrote: > passing NULL to a free function is not an error case. if it were, then > free(NULL) would crash. > > On Wed, Oct 3, 2012 at 12:59 PM, Tom Hacohen wrote: > >> I agree with Gustavo. This is as obviously an error

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Michael Blumenkrantz
passing NULL to a free function is not an error case. if it were, then free(NULL) would crash. On Wed, Oct 3, 2012 at 12:59 PM, Tom Hacohen wrote: > I agree with Gustavo. This is as obviously an error case, and errors > should be printed as such. It's not a convenience like making free check > fo

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Tom Hacohen
I agree with Gustavo. This is as obviously an error case, and errors should be printed as such. It's not a convenience like making free check for NULL, as deleting objects has more meaning than just freeing memory. I think one of the best improvements I've ever did to Evas was turning magic/nul

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-10-03 Thread Gustavo Sverzut Barbieri
Bad commit. At least if EVAS_MAGIC_SOMETHING variable is set we should bitch so we can debug these errors On Wednesday, October 3, 2012, Enlightenment SVN wrote: > Log: > probably the best commit I'll ever make: evas_object_del() now takes NULL > parameter without bitching > > > Author: di

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-06-14 Thread ChunEon Park
ssage- From: "ChunEon Park" To: ; ; Cc: Sent: 2012-06-13 (수) 19:32:32 Subject: Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas Not only image but other much functions depend on the engine now. It's awful to check the engine for every APIs. How about just put

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-06-13 Thread Michael Blumenkrantz
> > To: @lists.sourceforge.net>; @ > lists.sourceforge.net>; > Cc: > Sent: 2012-06-13 (수) 19:32:32 > Subject: Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas > > Not only image but other much functions depend on the engine now. >

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-06-13 Thread ChunEon Park
ssage- From: "ChunEon Park"@naver.com> To: @lists.sourceforge.net>; @lists.sourceforge.net>; Cc: Sent: 2012-06-13 (수) 19:32:32 Subject: Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas Not only image but other much functions depend on the engine now. It

Re: [E-devel] E SVN: discomfitor IN trunk/evas: . src/lib/canvas

2012-06-13 Thread ChunEon Park
Not only image but other much functions depend on the engine now. It's awful to check the engine for every APIs. How about just putting the information in doc? -Regards, Hermet- -Original Message- From: "Enlightenment SVN" To: ; Cc: Sent: 2012-06-