[#1378] differences between Module and Class ? — Mathieu Bouchard <matju@...>

25 messages 2003/08/11
[#1387] Re: differences between Module and Class ? — matz@... (Yukihiro Matsumoto) 2003/08/12

Hi,

[#1442] Re: differences between Module and Class ? — Mathieu Bouchard <matju@...> 2003/08/21

[#1406] _id2ref bug? — Ryan Pavlik <rpav@...>

While debugging some caching code, I've come across a segfault related

22 messages 2003/08/14
[#1407] Re: _id2ref bug? — matz@... (Yukihiro Matsumoto) 2003/08/14

Hi,

[#1413] Re: _id2ref bug? (REPRODUCED, short) — Ryan Pavlik <rpav@...> 2003/08/14

On Fri, 15 Aug 2003 01:57:18 +0900

Re: -Wall cleanup project

From: matz@... (Yukihiro Matsumoto)
Date: 2003-08-03 00:21:22 UTC
List: ruby-core #1331
Hello,

In message "-Wall cleanup project"
    on 03/08/03, Daniel Berger <djberg96@yahoo.com> writes:

|Here are my "patches" to Preview 7 to help cleanup the
|-Wall warnings for Suse Linux 8.0 with gcc 3.2.  Note
|that the largest offender is eval.c, which often
|complains with this warning:
|
|"variable `some_var' might be clobbered by `longjmp'
|or `vfork'"
|
|I tried declaring some of these as volatile just to
|see what would happen but that seemed to cause more
|problems.

 * do not use old diff format. It's unreadable.  I prefer -u
   (unified).

 * ignore warnings from variables marked as /* OK */ for example, 

     VALUE result;             /* OK */

   I checked and confirmed they are safe, regardless of warnings.

 * the functions below are for debug purpose.  just ignore.

|Other warnings:
|===============
|parse.y:4443: warning: `nodeline' defined but not used
|regex.c:2572: warning: `insert_op' defined but not
|used
|regex.c:1000: warning: `print_compiled_pattern'
|defined but not used

							matz.

In This Thread

Prev Next