[bittorrent] Introductory/endgame algorithms
Olaf van der Spek
olafvdspek at gmail.com
Fri Sep 30 05:51:53 EDT 2005
On 9/30/05, Bill Cox <bill at viasic.com> wrote:
> On Fri, 2005-09-30 at 10:05 +0200, Olaf van der Spek wrote:
> > On 9/30/05, Elliott Mitchell <ehem at m5p.com> wrote:
> > > >From: Olaf van der Spek <olafvdspek at gmail.com>
> > > > On 9/30/05, Elliott Mitchell <ehem at m5p.com> wrote:
> > > > > > http://libtorrent.rakshasa.no/
> > > > >
> > > > > Unfortunately two issues here. First, http://libtorrent.sourceforge.net/,
> > > > > there is already a library of the same name out there. Second, despite
> > > > > claims to the contrary, the world is not ruled by C++, quite a few new
> > > > > things are written in C. Just because you're using C, doesn't mean you
> > > > > aren't doing OO (sorry, rant time there).
> Ditto on the rant. Actually, most commercial code is still written in
> C, and for good (although debatable) reasons.
What's the source of that statement?
> > > > But what's the reason to use C instead of C++ in that case?
> > > Slightly better performance.
> Other reasons exist if you're doing a multi-programmer project.
> > Why (if you write equivalent code)?
> It runs just as fast then. We just have to avoid features, like virtual
> functions, in critical code. I find that in very critical code, I even
> have to avoid some C features such as structures, which organize data
> very poorly for cache performance.
But what part of your code is (highly) performance critical?
More information about the BitTorrent