[#1884] multiple exceptions for assert_raises — nobu.nokada@...

Hi,

14 messages 2003/12/04

[#1932] --enable-pthread broken? — Nathaniel Talbott <nathaniel@...>

[ruby-talk: 87759] and the surrounding thread seem to indicate that

29 messages 2003/12/11
[#1933] Re: --enable-pthread broken? — matz@... (Yukihiro Matsumoto) 2003/12/11

Hi,

[#1934] Re: --enable-pthread broken? — Nathaniel Talbott <nathaniel@...> 2003/12/11

On Dec 11, 2003, at 11:49, Yukihiro Matsumoto wrote:

[#1935] Re: --enable-pthread broken? — ts <decoux@...> 2003/12/11

>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:

[#1937] Re: --enable-pthread broken? — nobu.nokada@... 2003/12/11

Hi,

[#1938] Re: --enable-pthread broken? — Nathaniel Talbott <nathaniel@...> 2003/12/12

On Dec 11, 2003, at 16:10, nobu.nokada@softhome.net wrote:

[#1939] Re: --enable-pthread broken? — matz@... (Yukihiro Matsumoto) 2003/12/12

Hi,

[#1941] Re: --enable-pthread broken? — matz@... (Yukihiro Matsumoto) 2003/12/12

Hi,

[#1943] Re: --enable-pthread broken? — Nathaniel Talbott <nathaniel@...> 2003/12/12

On Dec 11, 2003, at 20:48, Yukihiro Matsumoto wrote:

[#1953] Re: --enable-pthread broken? — matz@... (Yukihiro Matsumoto) 2003/12/13

Hi,

[#1959] Re: --enable-pthread broken? — ts <decoux@...> 2003/12/14

>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:

[#1961] Re: --enable-pthread broken? — matz@... (Yukihiro Matsumoto) 2003/12/15

Hi,

[#1962] Re: --enable-pthread broken? — ts <decoux@...> 2003/12/15

>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:

[#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

11 messages 2003/12/11

[#1973] Where to install documentation — Dave Thomas <dave@...>

Folks:

48 messages 2003/12/15
[#1982] Re: Where to install documentation — Eric Hodel <drbrain@...7.net> 2003/12/15

Dave Thomas (dave@pragprog.com) wrote:

[#1984] Re: Where to install documentation — Dave Thomas <dave@...> 2003/12/15

[#1991] Re: Where to install documentation — "Gavin Sinclair" <gsinclair@...> 2003/12/16

>

[#1992] Re: Where to install documentation — Dave Thomas <dave@...> 2003/12/16

[#2000] Re: Where to install documentation — Minero Aoki <aamine@...> 2003/12/16

Hi,

[#2002] Re: Where to install documentation — Dave Thomas <dave@...> 2003/12/16

[#2037] --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...>

I've finally been able to test my application under load using the

25 messages 2003/12/23
[#2038] Re: --enable-pthread still segfaults... — matz@... (Yukihiro Matsumoto) 2003/12/23

Hi,

[#2039] Re: --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...> 2003/12/23

On Dec 23, 2003, at 14:17, Yukihiro Matsumoto wrote:

[#2040] Re: --enable-pthread still segfaults... — matz@... (Yukihiro Matsumoto) 2003/12/23

Hi,

[#2041] Re: --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...> 2003/12/23

On Dec 23, 2003, at 14:34, Yukihiro Matsumoto wrote:

[#2042] Re: --enable-pthread still segfaults... — matz@... (Yukihiro Matsumoto) 2003/12/23

Hi,

[#2043] Re: --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...> 2003/12/23

On Dec 23, 2003, at 14:44, Yukihiro Matsumoto wrote:

[#2045] Re: --enable-pthread still segfaults... — matz@... (Yukihiro Matsumoto) 2003/12/23

Hi,

[#2046] Re: --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...> 2003/12/23

> I'm afraid you're using old configure file. Can you wipe off old

[#2049] Re: --enable-pthread still segfaults... — Nathaniel Talbott <nathaniel@...> 2003/12/23

On Dec 23, 2003, at 15:18, Nathaniel Talbott wrote:

[#2050] Re: --enable-pthread still segfaults... — matz@... (Yukihiro Matsumoto) 2003/12/23

In message "Re: --enable-pthread still segfaults..."

[#2122] Bad interaction between timeout.rb and --enable-pthread — Nathaniel Talbott <nathaniel@...>

Here's a testcase that shows the problem:

13 messages 2003/12/31
[#2123] sleep is broken with --enable-pthread [Was: Bad interaction between timeout.rb and --enable-pthread] — Nathaniel Talbott <nathaniel@...> 2003/12/31

I should have reduced it more before posting...

Re: -Wall warnings from 1.8.1 p3

From: Daniel Berger <djberge@...>
Date: 2003-12-10 15:39:35 UTC
List: ruby-core #1925
nobu.nokada@softhome.net wrote:
> 
> Hi,
> 
> At Wed, 10 Dec 2003 03:42:00 +0900,
> Daniel Berger wrote:
> > 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)
> 
> Replace %o with %lo.

That fixes it.  Thanks.

> > From dl.c:
> >
> > dl.c:167: warning: subscript has type `char'
> > dl.c:169: warning: subscript has type `char'
> 
> Is it warned at other places where ISDIGIT() is used?  Then we
> might need to change ISALPHA() and so on.  Although I guess
> this warnings are useless at all for ctype macros, and ignoring
> would be best.

So it would seem.  Here's a few:

rubyext.c: In function `rb_syck_mktime':
rubyext.c:208: warning: subscript has type `char'
rubyext.c:213: warning: subscript has type `char'
rubyext.c:218: warning: subscript has type `char'
rubyext.c:223: warning: subscript has type `char'
rubyext.c:228: warning: subscript has type `char'
rubyext.c: In function `yaml_org_handler':
rubyext.c:489: warning: subscript has type `char'
rubyext.c:494: warning: subscript has type `char'

> 
> > > > 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.
> 
> Ok, I agree to Eric.

Ok, sounds good.
 
> > > > 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.
> 
> Do you know where alloca() is declared?

In alloca.h.  I think the relevant thread is ruby-talk 55208.  Although
that thread refers to FXRuby, I suspect it's the same issue in core
Ruby.
 
> > 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?
> 
> It is sometimes asked.  Actually, it can be suppressed by
> double parentheses in GCC, but matz dislike it.

Yeah, I don't necessarily believe in catering to gcc quirks, either.

Regards,

Dan

In This Thread