Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!ucsdhub!hp-sdd!hplabs!hpfcdc!hpldola!hp-lsd!hp-col!bdale
From: bdale@hp-col.HP.COM (Bdale Garbee)
Newsgroups: comp.lang.c++
Subject: Re: TCP/IP in C++?
Message-ID: <1200002@hp-col.HP.COM>
Date: 22 Feb 89 03:01:16 GMT
References: <4800053@m.cs.uiuc.edu>
Organization: HP Colorado Springs Division
Lines: 13

>Seems a lot of ugly fluff could disappear...I could trust the source more.

Ok.  Given equal amounts of effort to develop and test each implemenation, I
agree that it'd be easier to understand, and therefore trust, a C++ 
implementation.  My comments were directed from an environment in which I have
a couple of well-wrung-out TCP/IP implementations that I understand to base
future code on, and starting over just for the sake of a language would not 
provide a reasonable return on investment...

Layered protocols *do* make neat examples though... hadn't thought about that
until this discussion...

Bdale