On Wed, 7 Dec 2011 12:06:46 +0100 Cedric BAIL <cedric.b...@free.fr> said:
> On Wed, Dec 7, 2011 at 11:50 AM, Vincent Torri <vincent.to...@gmail.com> > wrote: > > On Wed, Dec 7, 2011 at 10:48 AM, Joerg Sonnenberger <jo...@britannica.bec.de > >> wrote: > >> On Wed, Dec 07, 2011 at 02:29:17AM -0500, Christopher Michael wrote: > >> > On 12/06/11 20:10, Enlightenment SVN wrote: > >> > > Log: > >> > > NO! you break api. you made my e sit here with a segv in a getenv. > >> > > because now many libraries and api's don't have prototyopes for > >> > > malloc/calloc and much more and this goes horribly wrong especially > >> on > >> > > 64bit! the eina headers have provided these includes historically > >> and > >> > > removing them is a BREAK in api. apps that used to compile and run > >> > > just fine now don't. it's unacceptable to break api. > >> > > > >> > > i'm stuck here in unity for crying out loud! this deservves a big > >> FAT > >> > > REVERT for that! :-P > >> > > > >> > AHMEN !!! To force ANYONE into Unity, is just extra pain that "we" > >> > should not have to go through. Raster, I am with you on this one > >> > regardless of the reason. To force something to use Unity is pain > >> > enough...the fact that EFL in general would break this much is not > >> > acceptible...period. > >> > >> Seriously, if you don't stop compilation on missing prototypes, you are > >> doing something wrong. I do not consider this to be an API breakage. > >> Headers should include just what they need -- e.g. if they directly use > >> a type or macro. > >> > > > > I agree. The eina header should just be self consistent (i mean : include > > what is really necessary). If no stdlib.h stuff is used in the headers, > > then stdlib.h can be removed. It's the source file including the eina > > header that is not including a necessary header file > > That was my point of view to, but raster is right. As people using EFL > weren't require to include <stdlib.h> in there file, they didn't. > Changing this, break their apps, so it's an API break. That's sad and > bad, but there is little we can do. For 2.0, in 10 years, we can fix > that, but now we are stuck with this include. correct. if this is good or bad (we include stdlib.h and what not) is now irrelevant. applications depend on that feature - even our OWN efl libs (efreet, ecore etc. etc.) rely on it - thus me being grumpily stuck in unity with e barfing at some weird place - getenv(). reality is anyone else using eina may end up in a similar position and that makes for an api break - if we like it or not, it's compatibility we have to maintain. we can change it at 2.0 when we are allowed to break things - but until that day ... we can't :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
