On Sun, 15 Aug 2010 10:30:10 +1000 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> well i'm almost willing to say all the eina threadsafe stuff should probably > be removed for efl 1.0.0 due to its immaturity. it's not small nad this will > piss stu off - but most of efl has had years of godo testing even with no test > suties via things like e, elementary, freebox, etc. etc. so its rather solid. > small added bits here and there are probably ok - like adding an accessor or a > trivial function. some things have had api for a long time and are missing > internal hooks (evas engine stuff in some cases) but the api is right (i'm > pretty sure) and designed for the right reasons, just the internal support is > not there yet. alpha is expected to be buggy - so fixing bugs is not something > we should care about freeze-wise. this freeze was simply so we can fix up code > formatting, readme's, installed files (so versions, sonames etc.) without > having to wrestle with a moving target. i am not averse to having an alpha2, > alpha3 etc. etc. > > so eina threadsafe stuff - very very very immature. not what i'd call "having > stood the test of time" by any stretch. regardless if there is a test suite. > api's only stand or fall by the test of time and real world usage. you get a > bonus if the api designer has done it maaaaaaaaaaaaaaaaaany times before, but > still is not totally there even then. > I have no problem with pushing this off to 1.1 or whenever. -- Mike Blumenkrantz Zentific: Our boolean values are huge. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
