02-01-2004
pid can be less than zero, equal to zero, or greater than zero. You already tested for equal to zero. And you tested for less than zero.
That means that pid must be greater than zero when it reaches that code. Putting in an explicit test will not change the way the program runs. And it will slow it down, but not measurably so.
Still I would put the explicit test in. This makes the code more readable. It also makes "paragraph 3" more self sufficient. These things make future changes to the program easier.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What is a fork? Why would one create a fork? What are the advantages and disadvantages of using a fork?
Please advise.
Thank You.
Deepali (5 Replies)
Discussion started by: Deepali
5 Replies
2. UNIX for Dummies Questions & Answers
I have a basic question - how do I create and then use a mail list to be able to send a mailx email to multiple recipients.
I assume I create a test file using vi, containing the email addresses - but what is the format - are the addresses separated by ";", or by spaces, ....???
Is there a... (1 Reply)
Discussion started by: HikerLT
1 Replies
3. Programming
#include <stdio.h>
#include <string.h>
#include <sys/types.h>
#define MAX_COUNT 200
#define BUF_SIZE 100
void main(void)
{
pid_t pid;
int i;
char buf;
fork();
pid = getpid();
for (i = 1; i <= MAX_COUNT; i++) {
sprintf(buf,... (2 Replies)
Discussion started by: MKSRaja
2 Replies
4. Programming
Hello all.
I'm developing a filetransfer application, which is supposed to work sort of like dcc, with multiple transfers etc. Now i wonder what the best way to manage the transfers is. Should i fork() for each new transfer, hogging loads of memory or use pthreads? Maybe I can use select to see... (0 Replies)
Discussion started by: crippe
0 Replies
5. Programming
hi all
About this code
for (i = 1; i < n; i++)
if ((childpid = fork()) <= 0)
break;
I really can't understand the output .
and the way fork () return the value .
how about the process Id ,the child process Id and the parent ID
in this case
so please answer me soon (5 Replies)
Discussion started by: iwbasts
5 Replies
6. Programming
Hi everybody,
I wanna write a code to understand how fork works.
my target
--------------
-Parent creates a file(called temp) and writes into this file "1".Then it closes the file.
-Then parent creates a child and wait until execution of this child ends.
-Then child opens the same... (3 Replies)
Discussion started by: alexicopax
3 Replies
7. UNIX for Advanced & Expert Users
Hi,
I wrote a simple program for understanding the fork command. The code is as below
int main(void)
{
fork(); printf("hi 1 \n");
fork(); printf("hi 2 \n");
fork(); printf("hi 3 \n");
}
I am getting a variation in the number of times the printf is called if i remove the \n from each of... (1 Reply)
Discussion started by: xyz123456
1 Replies
8. Programming
Hi,
I wrote a simple program for understanding the fork command. The code is as below
int main(void)
{
fork(); printf("hi 1 \n");
fork(); printf("hi 2 \n");
fork(); printf("hi 3 \n");
}
I am getting a variation in the number of times the printf is called if i remove the \n from each... (2 Replies)
Discussion started by: xyz123456
2 Replies
9. Programming
does fork() spawn only the parent process, what if fork() is looped, does it spawn the parent and the child? (4 Replies)
Discussion started by: Peevish
4 Replies
10. UNIX for Dummies Questions & Answers
I'm trying to run a simple test on how to use fork(), i'm able to execute the child process first then the parent, but how can I execute parent then child..?
Thanks! (1 Reply)
Discussion started by: l flipboi l
1 Replies
LEARN ABOUT CENTOS
ppi::token::comment
PPI::Token::Comment(3) User Contributed Perl Documentation PPI::Token::Comment(3)
NAME
PPI::Token::Comment - A comment in Perl source code
INHERITANCE
PPI::Token::Comment
isa PPI::Token
isa PPI::Element
SYNOPSIS
# This is a PPI::Token::Comment
print "Hello World!"; # So it this
$string =~ s/ foo # This, unfortunately, is not :(
bar
/w;
DESCRIPTION
In PPI, comments are represented by "PPI::Token::Comment" objects.
These come in two flavours, line comment and inline comments.
A "line comment" is a comment that stands on its own line. These comments hold their own newline and whitespace (both leading and trailing)
as part of the one "PPI::Token::Comment" object.
An inline comment is a comment that appears after some code, and continues to the end of the line. This does not include whitespace, and
the terminating newlines is considered a separate PPI::Token::Whitespace token.
This is largely a convenience, simplifying a lot of normal code relating to the common things people do with comments.
Most commonly, it means when you "prune" or "delete" a comment, a line comment disappears taking the entire line with it, and an inline
comment is removed from the inside of the line, allowing the newline to drop back onto the end of the code, as you would expect.
It also means you can move comments around in blocks much more easily.
For now, this is a suitably handy way to do things. However, I do reserve the right to change my mind on this one if it gets dangerously
anachronistic somewhere down the line.
METHODS
Only very limited methods are available, beyond those provided by our parent PPI::Token and PPI::Element classes.
line
The "line" accessor returns true if the "PPI::Token::Comment" is a line comment, or false if it is an inline comment.
SUPPORT
See the support section in the main module.
AUTHOR
Adam Kennedy <adamk@cpan.org>
COPYRIGHT
Copyright 2001 - 2011 Adam Kennedy.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included with this module.
perl v5.16.3 2011-02-26 PPI::Token::Comment(3)