Talk:ANSI C with Unix

This is useless. Better to delete it than have no content at all
Um. Whatever. If it were deleted, someone would simply redo the whole thing and leave it here again. Why waste that time? The structure is fine, it just needs contributions to the reference sections. Anyway... a lot of the content for the lower sections is already up, for free (CC or the like). It could be aggregated here easily. My concern is more with the "with UNIX" part of the title. Clearly the present content reflects it to mean "using a POSIX shell, common command line tools, and the GNU compiler toolchain. This is only a tiny part of the picture. I suggest all shell script examples not be necessarily Bourne-again, or even Bourne compatible, but rather, use straight POSIX shell syntax only. This is not a scripting book, it's a C programming book. Further, the only C programming section title I really see so far that even have a hint of Unix is IPC (inter-process comms).
 * I agree

If you really want to make this a useful study reference, then the sections following C syntax should break down POSIX calls into categories. This does two things; first, it frees you from having GNU/Linux-only examples, and second, it provides a LOT more useful content to the user. Certainly, they can learn how to open, fprintf, and close files. Why not learn about fstat and stat? How big are files, regardless of their OS or filesystem? Why not learn symlink and unlink, this is Unix, right? One could cover twenty-five of the most commonly used POSIX system calls and increase the book's usefulness a hundredfold. Please do not simply re-invent KR, but with a bash & GCC primer.
 * I agree, there many of those!

One could learn, on GNU/Linux, with this book, and then immediately apply 100% of what they learn directly to an embedded distro, or 85% directly to a Mac OS X machine. Just a suggestion :) ...   65.112.197.16 (talk) 18:09, 5 June 2008 (UTC)
 * I agree that this can be deleted! Because it is 13 years old with just one person wrote something.
 * This book should not be initiated here, because it was conceived as part of a particular course in programming, in addition to other programming courses and is compared to Java. I suppose that the course is outdated or the students are not motivated to write this book. I started to help this project but cancelled my changes because I noticed that this is really a project for that course.
 * Also because there are many free books covering the topics.
 * maybe just to be polite and ask agreement of the original poster of this book.