Prev: FAQ 8.36 How do I fork a daemon process?
Next: FAQ 8.21 Where do I get the include files to do ioctl() or syscall()?
From: Phred Phungus on 9 Mar 2010 19:45
Ben Morrow wrote:
> No, I think someone has just incorrectly changed the tense of that
> sentence at some point in the past. I suspect what was meant is
> Simple files like errno.h, syscall.h and socket.h are fine, but the
> hard ones like ioctl.h nearly always need to be hand-edited.
>> My question is how syscall is different from C's
>> int status;
>> status = system("ls *");
>> FILE *fp;
>> fp = popen ("ls *", "r");
>> If I'm to rely on my own eyes reading syscall in _Programming Perl_, I
>> would say they were completely disparate notions.
> I don't understand the question. syscall is completely different from
> either system or popen (or ls, for that matter).
Yet you answered the question. Lew Pitcher used them synonymously in
one of his explanations, which are usually very careful and correct.
Maybe we have tendency to elide system call to sys call.