[#6864] ruby 1.8.4 rc breaks alias_method/rails in bad ways — "Ara.T.Howard" <ara.t.howard@...>

20 messages 2005/12/09
[#6870] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2005/12/12

Ara.T.Howard wrote:

[#6872] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, [ISO-8859-15] Florian Growrote:

[#6873] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — James Edward Gray II <james@...> 2005/12/12

On Dec 12, 2005, at 1:19 PM, ara.t.howard@noaa.gov wrote:

[#6874] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, James Edward Gray II wrote:

[#6891] Time.utc! and Time.localtime! — Daniel Hobe <hobe@...>

Writing a script yesterday I found out, much to my surprise, that the

16 messages 2005/12/14

[#6918] change to yaml in 1.8.4 — ara.t.howard@...

14 messages 2005/12/16

[#6934] 1.8.x, YAML, and release management — Ryan Davis <ryand-ruby@...>

I'm concerned that 1.8.3's acceptance of non-backwards-compatible

28 messages 2005/12/18

[#6996] Problems building 1.8.4 with VS8 C++ Express Edition (cl 14.00) — Austin Ziegler <halostatue@...>

Visual Studio C++ 2005 Express Edition (VS 8.0)

20 messages 2005/12/27

Re: ruby 1.8.4 preview2

From: "U.Nakamura" <usa@...>
Date: 2005-12-02 01:48:01 UTC
List: ruby-core #6817
Hello, nobu

In message "Re: ruby 1.8.4 preview2"
    on Dec.01,2005 23:36:11, <nobu@ruby-lang.org> wrote:
| I don't think so.  Just re-packaging with Bison 1.x, 2.0 or
| modified 2.1.

I agree that ruby distribution should be re-packaged with
another version of Bison.


| > +#if defined(YYBISON) && !defined(__STDC__) && (defined(_MSC_VER) || defined(__BORLANDC__))
| > +#define __STDC__ 1
| > +#endif
| 
| It isn't concerned with Visual C neither Borland C, and
| defining __STDC__ causes another error with a compiler which
| doesn't support prototypes.

(1) We know there are at least two compilers which support
    prototypes but don't defined __STDC__ macro.
(2) And Bison does not know such compilers.
(3) So, we should tell Bison it.

Of course this aproach doesn't help another non-ansi compilers.
But telling Bison that VC and BCC are ansi compilers is not
bad thing, I think.


Regards,
-- 
U.Nakamura <usa@garbagecollect.jp>



In This Thread