From: Andreas Schwab <schwab@suse.de>
To: "Dave Korn" <dave.korn@artimi.com>
Cc: "'jlh'" <jlh@gmx.ch>, "'Thomas R. Truscott'" <trt@cs.duke.edu>,
<gcc@gcc.gnu.org>
Subject: Re: Unomitted frame pointers
Date: Fri, 10 Dec 2004 16:33:00 -0000 [thread overview]
Message-ID: <jefz2ejepb.fsf@sykes.suse.de> (raw)
In-Reply-To: <NUTMEGeAzdfTVSxzW2300000613@NUTMEG.CAM.ARTIMI.COM> (Dave Korn's message of "Fri, 10 Dec 2004 16:23:59 -0000")
"Dave Korn" <dave.korn@artimi.com> writes:
> So really the safe way to code this is
>
> #define HELLOSTRING "Hello World!\n"
>
> write (2, HELLOSTRING, strlen(HELLOSTRING)-1);
No, it's
write (2, HELLOSTRING, strlen(HELLOSTRING));
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-12-10 16:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 15:44 Thomas R. Truscott
2004-12-10 16:05 ` jlh
2004-12-10 16:25 ` Dave Korn
2004-12-10 16:30 ` Nathan Sidwell
2004-12-10 16:41 ` Dave Korn
2004-12-10 17:54 ` Nathan Sidwell
2004-12-10 18:09 ` [OT] " Dave Korn
2004-12-10 16:33 ` Andreas Schwab [this message]
2004-12-10 16:40 ` Dave Korn
2004-12-10 16:55 ` Thomas R. Truscott
2004-12-10 17:26 ` Paul Brook
2004-12-11 11:53 ` Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2004-12-11 16:29 Sam Lauber
2004-12-12 1:33 ` Ian Lance Taylor
2004-12-11 16:26 Sam Lauber
2004-12-11 16:42 ` Nathan Sidwell
2004-12-12 0:09 ` Peter Barada
2004-12-11 16:15 Sam Lauber
2004-12-11 17:00 ` Eric Botcazou
2004-12-11 18:10 ` Robert Dewar
2004-12-13 6:16 ` Ranjit Mathew
2004-12-13 14:22 ` Robert Dewar
2004-12-13 23:36 ` Ben Elliston
2004-12-11 2:44 Sam Lauber
2004-12-11 15:40 ` Nathan Sidwell
2004-12-11 15:45 ` Andreas Schwab
2004-12-11 2:37 Sam Lauber
2004-12-10 5:26 Sam Lauber
2004-12-10 7:22 ` Eric Botcazou
2004-12-10 9:08 ` Richard Guenther
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=jefz2ejepb.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dave.korn@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=jlh@gmx.ch \
--cc=trt@cs.duke.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).