From: Steve Graegert <graegerts@gmail.com>
To: _z33 <timid.Gentoo@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Confusing Prototype
Date: Tue, 13 Sep 2005 20:34:27 +0200 [thread overview]
Message-ID: <6a00c8d505091311342f378eee@mail.gmail.com> (raw)
In-Reply-To: <dg5im3$etc$1@sea.gmane.org>
On 9/13/05, _z33 <timid.Gentoo@gmail.com> wrote:
> Steve Graegert wrote:
> >
> > Sorry, I do not fully agree.
>
> I knew I must have gone wrong somewhere ;-)
You haven't been wrong. The assumptions you made are quite correct.
I just disagreed on the fact that a pointer to the input buffer is
returned unconditionally.
Regards
\Steve
--
Steve Graegert <graegerts@gmail.com>
Software Consultancy {C/C++ && Java && .NET}
Mobile: +49 (176) 21248869
Office: +49 (9131) 7126409
prev parent reply other threads:[~2005-09-13 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 18:00 Confusing Prototype James Colannino
2005-09-12 12:30 ` _z33
2005-09-12 16:36 ` Steve Graegert
2005-09-13 3:56 ` _z33
2005-09-13 18:34 ` Steve Graegert [this message]
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=6a00c8d505091311342f378eee@mail.gmail.com \
--to=graegerts@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=timid.Gentoo@gmail.com \
/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).