From: Aaron Patterson <aaron@...>
Date: 2010-08-17T10:10:21+09:00
Subject: Re: which C standard

--bg08WKrSYDhXBjb5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 16, 2010 at 07:41:03PM +0900, Graham Agnew wrote:
> Hi,
>=20
> Which C standard does MRI use?  When I run configure on HP-UX, it seems
> to use C89.

MRI uses C89.

> I recently ran into an issue compiling the gherkin gem.  Seems that the
> C code in that gem makes use of C99 features like variable declarations
> in the middle of a block, and variable length arrays.
>=20
> Is it a bug in the gem to be using these features, or a bug in the MRI
> configure script to set the CFLAGS such that C89 is selected at compile
> time?

I'm not sure about this part.  Is your compiler enforcing the C89
standard because Ruby is compiled as C89?

The platforms I work on don't do that, so I'm not sure who to talk to.
It doesn't seem fair for MRI to force C89 upon gem authors, but at the
same time MRI is written using C89 standard.  :-/

Sorry if this wasn't too helpful.

--=20
Aaron Patterson
http://tenderlovemaking.com/

--bg08WKrSYDhXBjb5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iQEcBAEBAgAGBQJMaeF3AAoJEJUxcLy0/6/Gc/sIAJaV8ac0j0NQwM0oANXzHj8v
J51lnorOhWfSDPJrHZriJ6nj1cMDCHGig/lrEQdoeZpA8znsCd7MD8kGVBJxAM6r
cgwnCifiDJakiDChz3Zm7j4KAuM9q+g1KkFB2ev134KT6nJbw1dYmtYo/itgvZID
8bPLIKuNoMv9byBSJkw0k0ATQWQ5Efsyuv1Jsw42om2QY6tO5ptflScvdA/61lnS
Uky3Sa1zfSyBG35qNL+nQO21ZdlCOyrq2i9cwQP633At1452TVPcnYOCZECOKrZl
NYwMJ9lgokNfi1ZYkiz9bwNPSuHBoebtN36jwEE5hrxLGDn9GbInOx0cCTc0wnY=
=b2CY
-----END PGP SIGNATURE-----

--bg08WKrSYDhXBjb5--