-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Paolo Bonzini on 8/6/2008 3:09 PM:
|
|> I don't know how to measure or decide that. I believe I've seen such
|> usage before but I really can't say for sure, or point to an actual
|> example. Sorry.
|
| Here is all I could find:
|
http://www.google.com/codesearch?hl=en&lr=&q=AC_PROG_CC\(.*[%27%22]&sbtn=Search
|
|
| AC_PROG_CC("$INFORMIXC" cc gcc) # have to take care of INFORMIXC
|
| no arguments, but a quoted variable.
Sweet. My thoughts on using ac_prog_cc_list="$1" would then expand to
this code:
ac_prog_cc_list=""$INFORMIXC" cc gcc"
which (unless INFORMIXC contains whitespace) works out to the desired
effect, no m4_bpatsubst or eval needed.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiaVRIACgkQ84KuGfSFAYB9bACeMxH4fOZ9U6quQd9t27TRQ/5f
DHcAn2nVbZFmKmDwolsy8kwT2kEcjuY7
=Z919
-----END PGP SIGNATURE-----
