Search results for query: *

Most of the examples I have seen have been in C as opposed to a true OOP design (as in C++). Most C++ code relies on C linkage and uses stuff in sys/socket.h and files like that. For example, Addison Wesley publishes "Effective TCP/IP Programming" which is C, and the Stevens books are...

Those examples don't address the fundamental question of line discipline, how standard input isn't flushed to a receiving process until a newline is encountered. In the example above getchar() is never said to be unbuffered I/O l(like "read" from fd 0 with a 1 byte length). Here is...

http://www.erlenstar.demon.co.uk/unix/faq_4.html#SEC48

There are many possible answers to this question. A process group leader, like your shell for example, can send a signal to terminate it's child processes. A 'hangup' signal (generated by ctrl-C to a foreground process) for example, usually terminates a program. When you exit the shell/window...

In UNIX at least, all variables declared outside of a function (globally scoped within a translation unit) are placed in a zero initialized segment of memory. If you declare one with the same identifier in more than 1 file and link them together, you essentially are getting a namespace...

C++ thinks the function call to second() (within first) is a competing declaration. This is because C++ allows function overloading and thinks you are providing another prototype/declaration. How else would C++ know you didn't mean to declare another version of "second" which accepted...

For what it's worth, (1) signal(SIGCHLD, SIG_IGN) fixes the problem (2) My own registered handler only catches the first time! Not interested in re-registering the handler within the handler. It still doesn't explain why my signal handler gets "unregistered" after one use. That...

Hello, I have a simple socket program design to run on the same machine the clients will appear on. It's very simple, it just returns a unique number to shell (like a primary key). The reason is so concurrent shell scripts can use the number returned to name files without clobbering each others...