On Aug 19, 2010, at 1338 PT, Nicholas Marriott wrote:
I haven't done much with 2.x, but personally a two way core/extra
split
seems just fine. IMO splitting things into a twenty pieces or adding a
dozen --disable-foo options just makes things confusing and hard work
for developers, packagers and users.
It isn't as if libevent is so huge that anyone with truly specialist
needs couldn't butcher it up themselves easily enough.
As much as I'm anti-kitchen-sink (and believe me I am) it should be
pointed out that any modern operating system with support for mmap,
paging, and shared pages, will not have any issue with a larger
library footprint size. Generally, unless linked statically, the OS
will make use of pages referenced by the library based on the linked
application's needs. Even if linked statically, the common text
segments will generally still be shared - with the linker only pulling
object code for functions and globals actually referenced by the
linking code.
Yeah, I always think smaller is better, and in general I agree with
Thor, but the added features in 2.0 are not the end of the world nor
will it result in a huge footprint leap.
One thing I will honestly say I'm iffy on is the Windows support. I
think we should be targeting POSIX systems only.
-cl
***********************************************************************
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-users in the body.
