From: Johannes Sixt <j.sixt@viscovery.net>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] sideband.c: Use xmalloc() instead of variable-sized arrays.
Date: Wed, 09 Jan 2008 08:34:55 +0100 [thread overview]
Message-ID: <4784791F.6090904@viscovery.net> (raw)
In-Reply-To: <alpine.LFD.1.00.0801081154460.3054@xanadu.home>
Nicolas Pitre schrieb:
> On Tue, 8 Jan 2008, Johannes Sixt wrote:
>> How come we got along with this not very portable construct for so long?
>> Probably because the array sizes were computed from the results of
>> strlen() of string constants.
>
> Maybe because it isn't not so unportable anymore? I doubt that
> compilers that don't know about automatic arrays would be smart enough
> to notice the variable was actually a constant due to the strlen() of a
> constant string and just do like if there wasn't any variable for the
> array size.
I just tried it with Visual Age 6, and got this:
CC sideband.o
"sideband.c", line 22.18: 1506-195 (S) Integral constant expression with a
value greater than zero is required.
"sideband.c", line 62.51: 1506-195 (S) Integral constant expression with a
value greater than zero is required.
make: *** [sideband.o] Error 1
But before I got to this point I had to change all 'static inline' in
git-compat-util.h to plain 'static'. So this compiler is out of the game
anyway.
Having said that, I'd actually prefer to stay with variable-sized arrays
if they prove portable enough because we don't need the handful of free()s
on function exits. Junio, if you like I can resend patch 2/2 using
variable-sized arrays.
-- Hannes
next prev parent reply other threads:[~2008-01-09 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:24 [PATCH 1/2] sideband.c: Use xmalloc() instead of variable-sized arrays Johannes Sixt
2008-01-08 17:01 ` Nicolas Pitre
2008-01-09 7:34 ` Johannes Sixt [this message]
2008-01-09 7:53 ` Junio C Hamano
2008-01-09 8:06 ` Johannes Sixt
2008-01-09 19:14 ` Nicolas Pitre
2008-01-08 17:41 ` Junio C Hamano
2008-01-08 19:59 ` Nicolas Pitre
2008-01-08 20:13 ` Junio C Hamano
2008-01-08 20:44 ` Nicolas Pitre
2008-01-09 7:26 ` Johannes Sixt
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=4784791F.6090904@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.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).