From: Junio C Hamano <junkio@cox.net>
To: Jason Riedy <ejr@EECS.Berkeley.EDU>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Spell __attribute__ correctly in cache.h.
Date: Sun, 28 Aug 2005 03:14:27 -0700 [thread overview]
Message-ID: <7vll2mmkqk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <2655.1124832058@lotus.CS.Berkeley.EDU> (Jason Riedy's message of "Tue, 23 Aug 2005 14:20:58 -0700")
Jason Riedy <ejr@EECS.Berkeley.EDU> writes:
> If you're interested, I have a few patches in
> http://www.cs.berkeley.edu/~ejr/gits/git.git#portable
> that let git compile with xlc on AIX and Sun's non-c99
> cc on Solaris.
I've taken a look at them. Thanks.
> Changes:
> + Replace C99 array initializers with code.
I presume this is to help older compilers?
> + Replace unsetenv() and setenv() with older putenv().
I wonder how buggy various implementations of
putenv("THIS_ENV_VAR") are to remove the variable.
> + Include sys/time.h in daemon.c.
> + Fix ?: statements.
I do not have much problem with these two.
> + Replace zero-length array decls with [].
This I am ambivalent about. If we are just trying to help older
compilers (see your "array initializers" patch), we should be
doing C90 way of "array[1]" and teach users to subtract 1 from
the allocate count. While I do not have much objection against
using C99 flexible array member notation, I wonder how people
find being able to compile with older compilers a major issue..
next prev parent reply other threads:[~2005-08-28 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 4:10 [PATCH] Spell __attribute__ correctly in cache.h Jason Riedy
2005-08-19 9:04 ` Junio C Hamano
2005-08-19 14:58 ` Jason Riedy
2005-08-19 19:53 ` Junio C Hamano
2005-08-23 21:20 ` Jason Riedy
2005-08-28 10:14 ` Junio C Hamano [this message]
2005-08-28 17:11 ` Jason Riedy
2005-08-28 17:46 ` Linus Torvalds
2005-08-28 19:08 ` Antti-Juhani Kaijanaho
2005-08-28 19:48 ` Linus Torvalds
2005-08-29 8:17 ` Martijn Kuipers
2005-08-29 8:35 ` Antti-Juhani Kaijanaho
2005-08-29 8:55 ` Martijn Kuipers
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=7vll2mmkqk.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ejr@EECS.Berkeley.EDU \
--cc=git@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).