linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: linux prg <linux-c-programming@vger.kernel.org>
Subject: Re: exit(42)
Date: Fri, 24 Sep 2004 20:25:17 +0800	[thread overview]
Message-ID: <4154122D.3030403@hq.ntsp.nec.co.jp> (raw)
In-Reply-To: <20040924115759.6133.qmail@web52908.mail.yahoo.com>

it does have a benefit....
it could be useful to another app that is trying to check the
return value or exit status of your application

like in bash programming... many bash scripts rely on the
exit values of programs...



Ankit Jain wrote:

>well do any body know what does this mean?
>
>exit(42)
>
>and also when we say exit(0) or exit(1) then there is
>anyway to catch these values
>
>also when we return from main fn then what is the
>benfit?
>
>does it have any utilisation?
>
>thanks
>
>ankit
>
>________________________________________________________________________
>Yahoo! Messenger - Communicate instantly..."Ping" 
>your friends today! Download Messenger Now 
>http://uk.messenger.yahoo.com/download/index.html
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>  
>


  parent reply	other threads:[~2004-09-24 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 11:57 exit(42) Ankit Jain
2004-09-24 12:13 ` exit(42) Alphex Kaanoken
2004-09-24 12:25 ` Ron Michael Khu [this message]
2004-09-27  9:16   ` exit(42) Pankaj
2004-09-27 12:39     ` exit(42) Micha Feigin
2004-09-27 13:54       ` exit(42) Jon Masters
2004-09-24 12:29 ` exit(42) Luciano Moreira - igLnx
2004-09-24 16:33 ` exit(42) Jan-Benedict Glaw
2004-09-25  1:13 ` exit(42) Micha Feigin
2004-09-25 10:57   ` exit(42) rinku rathore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4154122D.3030403@hq.ntsp.nec.co.jp \
    --to=ronkhu@ntsp.nec.co.jp \
    --cc=ankitjain1580@yahoo.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).