From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Spell __attribute__ correctly in cache.h.
Date: Sun, 28 Aug 2005 10:11:25 -0700 [thread overview]
Message-ID: <19723.1125249085@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <7vll2mmkqk.fsf@assigned-by-dhcp.cox.net>
And Junio C Hamano writes:
- > + Replace C99 array initializers with code.
- I presume this is to help older compilers?
Yes, so it's relatively unimportant. I could work
around it in my situation; I only included it
because it's "necessary" for some Sun compilers on
older Solaris installations. A static gcc build
works well enough in my situation.
- > + Replace unsetenv() and setenv() with older putenv().
- I wonder how buggy various implementations of
- putenv("THIS_ENV_VAR") are to remove the variable.
I don't know, and it doesn't seem to matter in the git
code. I didn't see checks for existance, but I may have
missed something. Most uses replace a NULL with a
pointer to "", which is why I just used putenv("FOO=").
This is to cope with an older Solaris installation I
have to use. ugh. I can use a better compiler, but
I'm stuck with the system library. Other older systems
probably don't have unsetenv(), either.
The "right" way would be to twiddle the environ and
use execle, but that's nasty.
- > + Replace zero-length array decls with [].
- This I am ambivalent about.
I'm fine with requiring a limited C99 compiler. A
pedantic compiler will reject members with a length
of zero. 6.7.5.2 para1 requires a value greater than
zero for a constant array size. So the code now (with
[0] decls) is neither C89 nor C99.
Jason
next prev parent reply other threads:[~2005-08-28 17:11 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
2005-08-28 17:11 ` Jason Riedy [this message]
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=19723.1125249085@lotus.CS.Berkeley.EDU \
--to=ejr@eecs.berkeley.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).