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. Joerg ------------------------------------------------------------------------------ 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
