[#1094] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c — Dave Thomas <dave@...>

> * eval.c (rb_mod_autoload, rb_mod_autoload_p): new method;

12 messages 2003/05/29
[#1095] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c — nobu.nokada@... 2003/05/29

Hi,

Re: [ruby-cvs] ruby/ext/syck: ext/syck/handler.c (syck_hdlr_add_alias): add cast to avoid warning.

From: matz@... (Yukihiro Matsumoto)
Date: 2003-05-14 07:06:57 UTC
List: ruby-core #1034
Hi,

In message "Re: [ruby-cvs] ruby/ext/syck: ext/syck/handler.c (syck_hdlr_add_alias): add cast to avoid warning."
    on 03/05/14, why the lucky stiff <ruby-core@whytheluckystiff.net> writes:

|I've noticed that <st.h> has changed sometime between 1.6.8 and 1.8.0 to
|use the st_data_t typedef.  Is there a safe way to sniff between these two
|versions of the symbol table?  Adding st_data_t casts breaks 1.6.8
|compilation.

How about forgetting 1.6.x, since it will be obsolete once we've
released 1.8.0?

							matz.

In This Thread

Prev Next