[epiar-devel] Threads, Networking, etc..
eb0s at yahoo.com
Sun Dec 20 18:53:32 PST 2009
Ok that's fine we can stick to SDL, it makes sense if everything else is SDL. I didn't realize it had a networking portion that doesn't seem to be advertised too well. Also another item that made me happy about boost was it supported serialization but thats not too big a deal.
----- Original Message ----
From: Chris Thielen <cthielen at mac.com>
To: epiar-devel at epiar.net
Sent: Sun, December 20, 2009 6:42:51 PM
Subject: Re: [epiar-devel] Threads, Networking, etc..
Agreed! I've already lamented about our third party library bloat, but we should absolutely use SDL's included threading facilities for whatever's necessary. Note that things like SDL audio already use threading without letting you know, so we shouldn't introduce threading where not necessary.
SDL_net is also a really good decision. The SDL libraries may not add features often, but they're incredibly well tested across many platforms.
On Dec 20, 2009, at 6:05 PM, Chris Walton wrote:
> I've not used ACE, but I've researched it. It's quite heavyweight and
> seems grossly overdone for Epiar.
> commonc++ I've never heard of.
> Boost isn't a bad choice, plus it provides a bunch of other neat
> things (though you have to be careful, some boost constructs are
> super-slow despite being extremely well programmed).
> However, SDL already provides all those platform-independent things.
> Network support is provided by SDLNet, which is also programmed by Sam
> Lantinga. While I haven't worked with SDLNet, knowing that it's
> created by him pretty much tells me that it's of extremely high
> quality. Sam Lantinga is, among other things, the creator of SDL and
> lead programmer at Blizzard, and a coder that I respect very, very
> much. :)
> -- Chris
> On Mon, Dec 21, 2009 at 1:44 AM, Shawn Reynolds <eb0s at yahoo.com> wrote:
>> Hey Guys,
>> I was thinking we need some libraries to handle platform independent threading, networking and other things. I did some research and one of these below options might be nice. Does anyone have a preference or worked with any of these before? I want to avoid windows users having to use cygwin or minigw so anything that requires that should be out. I also think we should use a library that we can easily distributed and well documented. Personally I am leaning towards Boost but i have some concerns about distributing it.
>> epiar-devel mailing list
>> epiar-devel at epiar.net
> epiar-devel mailing list
> epiar-devel at epiar.net
epiar-devel mailing list
epiar-devel at epiar.net
More information about the epiar-devel