Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Mar 2001 21:31:56 -0700
From:      "fbsd" <fbsd@wbs-inc.com>
To:        "Gabriel Ambuehl" <gabriel_ambuehl@buz.ch>, "Kris Kennaway" <kris@FreeBSD.ORG>
Cc:        "Gabriel Ambuehl" <gabriel_ambuehl-fbquestions@buz.ch>, <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Re[2]: good book on UNIX TCP/IP socket programming in C++?
Message-ID:  <007c01c0b740$064a5aa0$0200fea9@infowest.com>
References:  <85286437044.20010327193622@buz.ch><20010327101309.A67416@citusc17.usc.edu> <147290010432.20010327203555@buz.ch>

next in thread | previous in thread | raw e-mail | index | archive | help

----- Original Message -----
From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To: Kris Kennaway <kris@FreeBSD.ORG>
Cc: Gabriel Ambuehl <gabriel_ambuehl-fbquestions@buz.ch>;
<freebsd-questions@FreeBSD.ORG>
Sent: Tuesday, March 27, 2001 11:35 AM
Subject: Re[2]: good book on UNIX TCP/IP socket programming in C++?


> -----BEGIN PGP SIGNED MESSAGE-----
>
> Hello Kris,
>
> Tuesday, March 27, 2001, 8:13:09 PM, you wrote:
> > As far as I know, there isn't a standardized C++ API for network
> > stuff; most C++ programs use the C socket API (the rest use some
> kind
> > of nonstandardized wrapper library).  Consequently, most/all of the
> > documentation talks about it from a C PoV.  You really can't get
> > around learning it - fortunately, it's pretty easy, especially if
> you
> > know C++.
>
>
> I currently don't know neither on a useable level (well, I'm able to
> do very easy patches but that's about it). The motivation for choosing
> C++ over C was the OO paradigm which I very much like and since it is
> reported to cause serious problems to get accustomed to C++ OO if you
> come from a C background, I wanted to avoid learning C in first
> place...
>

If you are familiar with OO programming in some other language you shouldn't
have a major problem.  The main problem in moving from C to C++ is that C++
does not force OO because it allows basically all of C.  So C programmers
can
keep on doing their old C stuff even when using a C++ compiler - they (we)
can
avoid going fully OO.

> > The best network programming reference is "UNIX Network Programming"
> > by W. Richard Stevens.
>
> Got his "TCP/IP illustrated" here. While everyone said it was very
> good,
> I found one of the O'Reillies to be better. Bookshop didn't have a
> single book on socket programming today (well, except for Java but
> that would hardly solve my Python performance problems ;-).
>
>
> Best regards,
>  Gabriel
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.0.2i
>
> iQEVAwUBOsDPfsZa2WpymlDxAQE35wgAl12WMMLHYSeLJgo9Q1sKajGyqT2JJ9og
> o8Al/BgJY3SvOamR8qK2V4kl34nY6eg864VHM+IP3P06hWUK7W2tyZWMLEsUhVhU
> WHE+BckkPPEedmLGsPNsaHUeOidniNmi1A35F7BAlYAU9sL8xnrKVEv9js0ijeaU
> /zO1/RxeM9OYTOj5Rhadbm5br86PYJmxM02TZqOyBfCV40NMtz4076UrnVdg1+Xy
> FYnSE6fJMjAOik5Fca8gI6jVKfHmI5rjpZ0ASefNPIA2DAFIWdjHtO6hzvp2+9OJ
> AG83ghnhqMUvokPizITxxXqEzJx/COTy5wEb2/+epHDVVYwZdy/IRg==
> =eTLW
> -----END PGP SIGNATURE-----
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007c01c0b740$064a5aa0$0200fea9>