I received the book I ordered and was very disappointed. The book said 
copyright 89 and 90 and had one chapter on TCP/IP. I don't even know if the 
web was around in '89. The C is a very strange syntax pre-ANSI I would say:

main(argc, argv)
int argc;
char *argv[];

    Bill

Bill Cunningham <nospam@nspam.invalid> wrote:
>    I received the book I ordered and was very disappointed. The book said 
> copyright 89 and 90 and had one chapter on TCP/IP. I don't even know if the 
> web was around in '89. The C is a very strange syntax pre-ANSI I would say:
> 
> main(argc, argv)
> int argc;
> char *argv[];

What book was it Bill?

Mark.

-- 
Mark Hobley
Linux User: #370818  http://markhobley.yi.org/

Mark Hobley wrote:

> What book was it Bill?

    It's called "UNIX networking" by Kochan and Wood. So much can be done 
with gettaddrinfo() now but the code in this book declares many objects of 
type struct sockaddr and all the other struct declared in socket.h and 
netdb.h.

Bill

On 2010-04-20, Bill Cunningham wrote:

>     I received the book I ordered and was very disappointed. The book said 
> copyright 89 and 90 and had one chapter on TCP/IP. I don't even know if the 
> web was around in '89. The C is a very strange syntax pre-ANSI I would say:
>
> main(argc, argv)
> int argc;
> char *argv[];

This is not a "very strange syntax", this is K&R C.
-- 
Unix is simple. It just takes a genius to understand its simplicity
	--Dennis M. Ritchie

"Bill Cunningham" <nospam@nspam.invalid> writes:
>Mark Hobley wrote:
>> What book was it Bill?

>    It's called "UNIX networking" by Kochan and Wood. So much can be done 
>with gettaddrinfo() now but the code in this book declares many objects of 
>type struct sockaddr and all the other struct declared in socket.h and 
>netdb.h.

I believe they told you to get a more modern book. The one you got was
written in the late 1980's as the copyright shows, and hasn't been
updated.  Lots of things change in 21+ years. :) Especially things
like ANSI C coming out in 1989. Before ANSI C, things did have to be
done as you quoted in your first post in this thread, not everyone
tracked pre-ANSI C coding standards and coded in the latest style back
then.  The '90's was an era for big changes in Unix, so be careful of
anything written in the '90s and before. 

The one they told you you should get was
http://www.amazon.com/Unix-Network-Programming-Sockets-Networking/dp/0131411551

Caution, this one started out fairly long ago too, but it has been
updated to reflect somewhat current stuff. Older editions are going 
to be different than the latest version in covering stuff, especially
modern programming APIs. 

At least you shouldn't have paid much for the Kochan and Wood book. I
have it (from when it was new), and its an okay book. Not anywhere
as good as the Stevens book though. 

"Doug McIntyre" <merlyn@geeks.org> wrote in message 
news:4bce0169$0$50145$8046368a@newsreader.iphouse.net...

> I believe they told you to get a more modern book.

Well I don't know who they are.

 The one you got was
> written in the late 1980's as the copyright shows, and hasn't been
> updated.  Lots of things change in 21+ years. :)

Indeed.

Especially things
> like ANSI C coming out in 1989. Before ANSI C, things did have to be
> done as you quoted in your first post in this thread, not everyone
> tracked pre-ANSI C coding standards and coded in the latest style back
> then.  The '90's was an era for big changes in Unix, so be careful of
> anything written in the '90s and before.
>
> The one they told you you should get was
> http://www.amazon.com/Unix-Network-Programming-Sockets-Networking/dp/0131411551

    You would go ahead and recommend this one then even though it's a little 
old itself?

> Caution, this one started out fairly long ago too, but it has been
> updated to reflect somewhat current stuff. Older editions are going
> to be different than the latest version in covering stuff, especially
> modern programming APIs.
[...] 

"Bill Cunningham" <nospam@nspam.invalid> writes:
>> http://www.amazon.com/Unix-Network-Programming-Sockets-Networking/dp/0131411551

>    You would go ahead and recommend this one then even though it's a little 
>old itself?

Yes, not alot of changes in the Networking API front since 2003.
Earlier editions were getting a bit dated, but this edition had a good
extensive refresh all around. While there may be some changes to some
aspect, this book has stood the time as the bible of TCP/IP socket programming.

In article <slrnhsrut0.fjj.vpm+news@pitchu.serengetty.fr>,
 Vivien MOREAU <vpm+news@serengetty.fr> wrote:

> On 2010-04-20, Bill Cunningham wrote:
> 
> >     I received the book I ordered and was very disappointed. The book said 
> > copyright 89 and 90 and had one chapter on TCP/IP. I don't even know if the 
> > web was around in '89. The C is a very strange syntax pre-ANSI I would say:
> >
> > main(argc, argv)
> > int argc;
> > char *argv[];
> 
> This is not a "very strange syntax", this is K&R C.

That's what he said: "pre-ANSI".

It's strange in the same way that Shakespearean English seems strange 
now.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***

Barry Margolin <barmar@alum.mit.edu> writes:
> In article <slrnhsrut0.fjj.vpm+news@pitchu.serengetty.fr>,
>  Vivien MOREAU <vpm+news@serengetty.fr> wrote:
>
>> On 2010-04-20, Bill Cunningham wrote:
>> 
>> >     I received the book I ordered and was very disappointed. The book said 
>> > copyright 89 and 90 and had one chapter on TCP/IP. I don't even know if the 
>> > web was around in '89. The C is a very strange syntax pre-ANSI I would say:
>> >
>> > main(argc, argv)
>> > int argc;
>> > char *argv[];
>> 
>> This is not a "very strange syntax", this is K&R C.
>
> That's what he said: "pre-ANSI".

This is not quite true. Except the missing return type, this is (as of
C99) still valid C, although the C-standard calls it 'obsolescent'.

In article <87aasxup2y.fsf@fever.mssgmbh.com>,
 Rainer Weikusat <rweikusat@mssgmbh.com> wrote:

> Barry Margolin <barmar@alum.mit.edu> writes:
> > In article <slrnhsrut0.fjj.vpm+news@pitchu.serengetty.fr>,
> >  Vivien MOREAU <vpm+news@serengetty.fr> wrote:
> >
> >> On 2010-04-20, Bill Cunningham wrote:
> >> 
> >> >     I received the book I ordered and was very disappointed. The book 
> >> >     said 
> >> > copyright 89 and 90 and had one chapter on TCP/IP. I don't even know if 
> >> > the 
> >> > web was around in '89. The C is a very strange syntax pre-ANSI I would 
> >> > say:
> >> >
> >> > main(argc, argv)
> >> > int argc;
> >> > char *argv[];
> >> 
> >> This is not a "very strange syntax", this is K&R C.
> >
> > That's what he said: "pre-ANSI".
> 
> This is not quite true. Except the missing return type, this is (as of
> C99) still valid C, although the C-standard calls it 'obsolescent'.

Who said it was invalid?  He just said it was strange.  As you pointed 
out, it's obsolescent, and has been out of fashion for two decades.  So 
it's quite unusual to see it these days.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***