From: Vamsi <krishna.vamsi@wipro.com>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Significance of using + before function calls.
Date: Wed, 15 Mar 2006 21:18:38 +0530 [thread overview]
Message-ID: <44183756.2030502@wipro.com> (raw)
In-Reply-To: <17431.59327.133701.804651@cerise.gclements.plus.com>
Glynn Clements wrote:
>Vamsi wrote:
>
>
>
>>i have seen a code snippet which starts with + symbol,
>>
>>+system("ls -l");
>>
>>
>
>I suspect that the "code snippet" in question comes from the output of
>"diff -u", and the + is part of the diff syntax, not part of the code.
>
>
>
No, i verified it is not a patch, or the output of diff.
Thank You.
next prev parent reply other threads:[~2006-03-15 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 12:59 Significance of using + before function calls Vamsi
2006-03-15 7:51 ` Steve Graegert
2006-03-15 7:58 ` Per Jessen
2006-03-15 12:11 ` Steve Graegert
2006-03-15 7:59 ` Joel M. Pareja
2006-03-15 13:40 ` Vamsi
2006-03-15 8:16 ` Joel M. Pareja
2006-03-15 10:09 ` Glynn Clements
2006-03-15 15:48 ` Vamsi [this message]
2006-03-15 20:34 ` Tomas Janousek
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=44183756.2030502@wipro.com \
--to=krishna.vamsi@wipro.com \
--cc=glynn@gclements.plus.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).