[#1834] New syck bug — Chad Fowler <chad@...>
There is a new syck bug that appears to be caused by the recent fix for
[#1836] exit inside test/unit — nobu.nokada@...
Hi,
On Dec 1, 2003, at 02:55, nobu.nokada@softhome.net wrote:
[#1843] DRb tests hang on OS X 10.3.1 — Nathaniel Talbott <nathaniel@...>
I haven't yet been able to test this on another platform to see if it
[#1846] Re: Constants, class variables and the cbase field — george.marrows@...
> What kind of behavior do you want (to change)? Remember you're saying
Hi,
On Monday 01 December 2003 06:44 pm, Yukihiro Matsumoto wrote:
Hi,
On Tuesday 02 December 2003 04:02 am, Yukihiro Matsumoto wrote:
[#1884] multiple exceptions for assert_raises — nobu.nokada@...
Hi,
Hi,
On Dec 4, 2003, at 02:34, Yukihiro Matsumoto wrote:
On Dec 4, 2003, at 01:35, nobu.nokada@softhome.net wrote:
On Dec 4, 2003, at 10:39, Nathaniel Talbott wrote:
[#1901] Test::Unit problem — "Sean E. Russell" <ser@...>
-----BEGIN PGP SIGNED MESSAGE-----
Hi,
[#1914] -Wall warnings from 1.8.1 p3 — Daniel Berger <djberge@...>
Here are some potentially significant warnings from 1.8.1 p3
nobu.nokada@softhome.net wrote:
[#1932] --enable-pthread broken? — Nathaniel Talbott <nathaniel@...>
[ruby-talk: 87759] and the surrounding thread seem to indicate that
Hi,
On Dec 11, 2003, at 11:49, Yukihiro Matsumoto wrote:
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
Hi,
On Dec 11, 2003, at 16:10, nobu.nokada@softhome.net wrote:
Hi,
Hi,
On Dec 11, 2003, at 20:48, Yukihiro Matsumoto wrote:
Hi,
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
[#1936] Can't define +@ for Symbol (plus ruby install problem) — "T. Onoma" <transami@...>
I wanted to see if the +@ problem was fixed in 1.8.1 preview 3 but when I do
Hi,
On Friday 12 December 2003 02:39 am, Yukihiro Matsumoto wrote:
Hi,
Hi.
Hi,
[#1973] Where to install documentation — Dave Thomas <dave@...>
Folks:
Hi,
Dave Thomas (dave@pragprog.com) wrote:
>
>> Using the standard install.rb, anything you include in a project's
Hi,
On Tue, Dec 16, 2003 at 03:52:26PM +0900, Dave Thomas wrote:
Hi,
[#2013] Mixin Module, Possible Bug? — "T. Onoma" <transami@...>
According to Pickaxe, Ch. 19, pg. 245, under Mixin Modules:
[#2037] --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...>
I've finally been able to test my application under load using the
Hi,
On Dec 23, 2003, at 14:17, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 14:34, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 14:44, Yukihiro Matsumoto wrote:
Hi,
> I'm afraid you're using old configure file. Can you wipe off old
On Dec 23, 2003, at 15:18, Nathaniel Talbott wrote:
In message "Re: --enable-pthread still segfaults..."
On Dec 23, 2003, at 16:34, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 17:04, Yukihiro Matsumoto wrote:
Hi,
On Dec 23, 2003, at 17:29, Yukihiro Matsumoto wrote:
Hi,
[#2071] rdoc is broken in 1.8.1 — Alexander Bokovoy <a.bokovoy@...>
Greetings!
[#2084] Error with Socket.getaddrinfo on OS X — Richard Kilmer <rich@...>
On OS X Panther:
[#2101] Can't call to_s on a frozen Date — Gavin Sinclair <gsinclair@...>
Interesting...
[#2102] syck segfaults when used in rdoc — Alexander Bokovoy <a.bokovoy@...>
Greetings!
>>>>> "A" == Alexander Bokovoy <a.bokovoy@sam-solutions.net> writes:
On Sun, Dec 28, 2003 at 11:41:49PM +0900, ts wrote:
>>>>> "A" == Alexander Bokovoy <a.bokovoy@sam-solutions.net> writes:
Hi,
[#2122] Bad interaction between timeout.rb and --enable-pthread — Nathaniel Talbott <nathaniel@...>
Here's a testcase that shows the problem:
I should have reduced it more before posting...
Nathaniel Talbott wrote:
Hi,
Hi,
On Jan 1, 2004, at 11:29, Yukihiro Matsumoto wrote:
On Jan 1, 2004, at 12:14, Nathaniel Talbott wrote:
Re: -Wall warnings from 1.8.1 p3
nobu.nokada@softhome.net wrote: > > Hi, > > At Tue, 9 Dec 2003 02:43:22 +0900, > Daniel Berger wrote: > > error.c:645: warning: `init_syserr' declared `static' but never defined > > > > file.c:329: warning: unsigned int format, different type arg (arg 3) > > > > gc.c:582: warning: unused variable `tmp' > > gc.c:658: warning: unused variable `ret' > > > > bigdecimal.c:106: warning: int format, different type arg (arg 3) > > > > curses.c:665: warning: `curses_ungetmouse' defined but not used > > curses.c:1264: warning: `window_bkgdset' defined but not used > > curses.c:1276: warning: `window_bkgd' defined but not used > > curses.c:1289: warning: `window_getbkgd' defined but not used > > > > dl.c: In function `dlsizeof': > > dl.c:167: warning: subscript has type `char' > > > > iconv.c: In function `iconv_convert': > > iconv.c:429: warning: int format, different type arg (arg 3) > > iconv.c: In function `Init_iconv': > > iconv.c:839: warning: unused variable `metaclass' > > > > pty.c: In function `getDevice': > > pty.c:343: warning: unused variable `p' > > pty.c:345: warning: unused variable `MasterName' > > pty.c: At top level: > > pty.c:89: warning: `MasterDevice' defined but not used > > pty.c:90: warning: `SlaveDevice' defined but not used > > pty.c:91: warning: `deviceNo' defined but not used > > pty.c:404: warning: `freeDevice' defined but not used > > > > socket.c: In function `port_str': > > socket.c:599: warning: int format, different type arg (arg 4) > > socket.c: In function `sock_s_getaddrinfo': > > socket.c:2109: warning: int format, different type arg (arg 4) > > socket.c: In function `sock_s_getnameinfo': > > socket.c:2228: warning: int format, different type arg (arg 4) > > > > rubyext.c: In function `rb_syck_compile': > > rubyext.c:96: warning: implicit declaration of function `syck_parser_assign_io' > > Does following patch clean these warnings? It cleaned most of them, but some remain: The file.c warning still (strangely) remains: file.c: In function `rb_stat_inspect': file.c:329: warning: unsigned int format, different type arg (arg 3) From window_bkgd in curses.c (as opposed to window_bkgdset before): curses.c:1278: warning: `window_bkgd' defined but not used curses.c:1291: warning: `window_getbkgd' defined but not used Should I wrap that function in a "#ifdef USE_COLOR" as well? From dl.c: dl.c:167: warning: subscript has type `char' dl.c:169: warning: subscript has type `char' > > > eval.c:9032: warning: `limit' might be used uninitialized in this function > > > > process.c: In function `rb_syswait': > > process.c:909: warning: `hfunc' might be used uninitialized in this function > > process.c:909: warning: `qfunc' might be used uninitialized in this function > > process.c:909: warning: `ifunc' might be used uninitialized in this function > > > > socket.c: In function `ipaddr': > > socket.c:660: warning: `addr1' might be used uninitialized in this function > > socket.c: In function `init_inetsock_internal': > > socket.c:897: warning: `syscall' might be used uninitialized in this function > > These are used conditionally. As for the last one, I guess > `status' should be warned rather than it. Ok. > > > sym.c:365: warning: unused variable `guard' > > I think this must be a "volatile pointer" instead of a "pointer > to volatile". > > > numeric.c:791: warning: implicit declaration of function `finite' > > Does math.h on Solaris lack finite()? Looks like it's defined in ieeefp.h on sun. I added #if defined(sun) #include <ieeefp.h> #endif That seemed to work. > > > parse.y:4443: warning: `nodeline' defined but not used > > This and nodetype() are for debug use. Ok. > > > socket.c: In function `bsock_getsockopt': > > socket.c:317: warning: implicit declaration of function `alloca' > > ALLOCA_N() macro is used in many place, why is it warned only > here? Actually, that warning shows up in many places, but that warning has been brought up on the list separately, so I didn't want to list them all again. > > > bigdecimal.c:1582: warning: `VpIsNegDoubleZero' defined but not used > > bigdecimal.c:3573: warning: `VpItoV' defined but not used > > I'm not sure whether these are planned to use or not. Ok. > > > rubyext.c: In function `syck_set_model': > > rubyext.c:681: warning: implicit declaration of function `syck_parser_set_input_type' > > I suspect this should be declared in syck.h, but not sure. > Since other syck stuff are tool-generated, only _why can fix > them. Ok. <snip> Hope that helps. Regards, Dan PS - Do you care about this warning? "warning: suggest parentheses around assignment used as truth value". If not, do you happen to know the option to disable that warning?