ruby 1.8.0 preview5

[Yukihiro Matsumoto]

Hello,

I just put preview5 archive on the ftp server.

ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.0-preview5.tar.gz

Unless something wrong happens, this would be the last preview before
the final 1.8.0 release.

matz.

 

[Cedric Foll]

Hello,

I just put preview5 archive on the ftp server.

ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.0-preview5.tar.gz

Unless something wrong happens, this would be the last preview before
the final 1.8.0 release.

matz.

Thanks for this gift matz.
The day of my birthday!

 

[gabriele renzi]

il Mon, 28 Jul 2003 17:37:53 +0900, (e-mail address removed) (Yukihiro
Matsumoto) ha scritto::

Hello,

I just put preview5 archive on the ftp server.

ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.0-preview5.tar.gz

Unless something wrong happens, this would be the last preview before
the final 1.8.0 release.

matz.

somehan run rubicon over this ?
I did and got various errors.. is it ok ?

 

[why the lucky stiff]

Looks like 'syck' still doesn't #include the header files it needs
(stdlib.h, string.h, ctype.h), so it's possible it will crash on platforms
where the size of provided arguments doesn't match the size expected.

Checking these in now.

_why

 

[the_rev_dharma_roadkill]

Hello,

I just put preview5 archive on the ftp server.

ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.0-preview5.tar.gz

Unless something wrong happens, this would be the last preview before
the final 1.8.0 release.

matz.

Looks pretty good on Tru64 5.1A (osf1 5.1a). Fewer compiler warnings
than preview4 and the stuff you said you fixed looks fixed. See below
for the rest:

29 warnings like this (signed/unsigned ptr), down from 95 in preview4:
cc: Warning: io.c, line 868: In the initializer for p, the referenced
type of th
e pointer value "((f)->_ptr)" is "unsigned char", which is not
compatible with "
const char" because they differ by signed/unsigned attribute.
(ptrmismatch1)
const char *p = READ_DATA_PENDING_PTR(f);
----------------------------^
I'm not very worried about those.

A warning you said could be ignored:
cc: Warning: stubs.c, line 94: Source file does not contain any
declarations. (e
mptyfile)
#endif
------^

A warning due to _XOPEN_SOURCE_EXTENDED not set in curses.h, probably
not very important and dangerous to fix:
cc: Warning: curses.c, line 434: In this statement, "keyname(...)" of
type "int"
, is being converted to "pointer to const char". (cvtdiftypes)
name = keyname(NUM2INT(c));
--^

And that's it, no more warnings. Thanks matz!

Doug

 

[daz]

Looks good to me. This release fixes the previously reported problem for
linking the OpenSSL extension on Red Hat Linux 8.0. Also checked it for
FXRuby and SWIG and all seems well.

Thanks very much, Matz (and all of the other core developers)!

.... who must have been under quite a lot of pressure
in recent weeks. Thank you all.


Dave Butcher

 

[George Marrows]

I'm fairly sure I saw something from Matz saying that post-1.8.0 he
wanted to take some time to bring Rubicon up to date and to use in a
test-first way for future releases. I can't find it now, and there's
always the chance I'm simply putting words in his mouth

-- George

 

[Aron Griffis]

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello,

In order to build with SOCKS support, the attached patch is required.

Also note that --disable-socks doesn't work if SOCKS_SERVER is set in
the environment. In order to build without socks support, it seems to
be necessary to unset SOCKS_SERVER.

Aron

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="ruby-1.8.0_pre2-socks.patch"

--- ruby-1.8.0/ext/socket/socket.c.old 2003-01-16 02:47:50.000000000 -0500
+++ ruby-1.8.0/ext/socket/socket.c 2003-05-22 15:06:31.000000000 -0400
@@ -991,7 +991,7 @@
init = 1;
}

- return init_inetsock(class, host, serv, Qnil, Qnil, INET_SOCKS);
+ return init_inetsock(sock, host, serv, Qnil, Qnil, INET_SOCKS);
}

#ifdef SOCKS5

--J2SCkAp4GZ/dPZZf--

 

[Yukihiro Matsumoto]

Hello,

In message "Re: ruby 1.8.0 preview5"

|In order to build with SOCKS support, the attached patch is required.

Confirmed. Thank you for the fix.

matz.

 

[nobu.nokada]

Hi,

At Wed, 30 Jul 2003 11:19:54 +0900,

29 warnings like this (signed/unsigned ptr), down from 95 in preview4:
cc: Warning: io.c, line 868: In the initializer for p, the referenced
type of th
e pointer value "((f)->_ptr)" is "unsigned char", which is not
compatible with "
const char" because they differ by signed/unsigned attribute.
(ptrmismatch1)
const char *p = READ_DATA_PENDING_PTR(f);
----------------------------^
I'm not very worried about those.

How is FILE_READPTR defined in config.h?

A warning you said could be ignored:
cc: Warning: stubs.c, line 94: Source file does not contain any
declarations. (e
mptyfile)
#endif
------^

Although the warning is definitely OK to ignore, does inserting
this line at the top suppress it?

extern int ruby_tcltk_stubs();

Or just comments suppress it?

A warning due to _XOPEN_SOURCE_EXTENDED not set in curses.h, probably
not very important and dangerous to fix:
cc: Warning: curses.c, line 434: In this statement, "keyname(...)" of
type "int"
, is being converted to "pointer to const char". (cvtdiftypes)
name = keyname(NUM2INT(c));
--^

Agree.