Date: Mon, 19 Oct 2009 05:46:20 +0200 From: Polytropon <freebsd@edvax.de> To: Robert Huff <roberthuff@rcn.com> Cc: Polytropon <freebsd@edvax.de>, Glen Barber <glen.j.barber@gmail.com>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: need C help, passing char buffer[] by-value.... Message-ID: <20091019054620.9cc1b05c.freebsd@edvax.de> In-Reply-To: <19163.56681.724615.44106@jerusalem.litteratus.org> References: <20091019013337.GA9522@thought.org> <20091019040229.b4e11bbc.freebsd@edvax.de> <4ad871310910181916q655dec06k72b1e7577751751e@mail.gmail.com> <19163.56681.724615.44106@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Oct 2009 23:30:49 -0400, Robert Huff <roberthuff@rcn.com> wrote: > > Glen Barber writes: > > > >> // redo, skip TAGS > > > > > > Is this C or C++ source code? I always thought // was C++ > > > specific... > > > > > > > "//" comments are recognized by both C and C++. > > How about "... are recognized by both C++ and more recent versions > of C."? That's what I thought. In fact, I *had* C programs containing the // comments, but they failed to compile. After changing the // to /* ... */ it worked. Maybe that's not an issue anymore, but I've been told by a long-time C programmer that // should be kept out of C code for maximum compatibility. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091019054620.9cc1b05c.freebsd>