very basic C question--K&R on a Mac

[Dan Pop]

K&R is full of example functions,
which have the same name as standard functions.
It is something that you will have to continue to watch out for.

Easier said than done. How is a beginner supposed to know the names
of the standard library functions?

Dan

 

[pete]

Easier said than done. How is a beginner supposed to know the names
of the standard library functions?

He'll have to look up all of the functions from the chapters,
in the index,
to find out if they are also the names of library functions.

 

[pete]

Dan Pop wrote:

He'll have to look up all of the functions from the chapters,
in the index,
to find out if they are also the names of library functions.

I forgot that he's using K&R and not K&R2.
He's going to need a different reference.

http://anubis.dkuug.dk/jtc1/sc22/wg14/www/docs/n869/

 

[Dan Pop]

He'll have to look up all of the functions from the chapters,
in the index,
to find out if they are also the names of library functions.

This is the last thing you want to do when reading K&R2 for the first
time: it breaks your focus on the things that really matter at that point.

You can start worrying about standard library function names later, by the
time you're fit for studying Appendix B.

Dan

 

[Dan Pop]

I forgot that he's using K&R and not K&R2.
He's going to need a different reference.

http://anubis.dkuug.dk/jtc1/sc22/wg14/www/docs/n869/

That document is not an accurate reference for *any* C standard (it
contains plenty of functions that are not part of the standard C89 library
and it's missing at least one function from the standard C99 library),
so why should he bother?

Dan

 

[pete]

That document is not an accurate reference for *any* C standard (it
contains plenty of functions that are not part of the standard
C89 library
and it's missing at least one function from the standard C99 library),
so why should he bother?

His problem is that he's compiling functions from K&R,
some of which have the same names as some standard library functions.

Any function in K&R1, which is defined in N869,
is part of the C89 standard library.
Any function in K&R1, which is not defined in N869,
is not part of the C89 standard library.

N869 is free, and the point of using K&R1,
is that his resources are limited.
"I can't afford the newer second edition"

 

[Dan Pop]

His problem is that he's compiling functions from K&R,
some of which have the same names as some standard library functions.

Could you, please, point out, which functions that have the same names as
some standard library functions is he using? I can't find any conflict
between the names used by the last example in chapter 5 and the standard
C library. Sure, the program uses printf, strcmp and atof, but it doesn't
define them.

His problem is that his implementation declares some of the user name
space identifiers used by that program, most likely as macros.

Any function in K&R1, which is defined in N869,
is part of the C89 standard library.
Any function in K&R1, which is not defined in N869,
is not part of the C89 standard library.

How could this help him with his problem? Neither comp nor exch, the
identifiers creating him problems, are mentioned in N869 as macro names,
are they?

N869 is free, and the point of using K&R1,
is that his resources are limited.
"I can't afford the newer second edition"

It might be free, but it doesn't solve his problem. So, what exactly is
your point?

Dan

 

[pete]

Dan Pop wrote:

Could you, please, point out,
which functions that have the same names as
some standard library functions is he using?

I may have misunderstood his problem.