[#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: ext/syck problems

From: why the lucky stiff <ruby-core@...>
Date: 2003-05-13 06:20:00 UTC
List: ruby-core #1018
U.Nakamura (usa@osb.att.ne.jp) wrote:
> 
> ext/syck was imported to the repository, however, we can see
> some problems.
> 

Yes, let's go through these and get them extinguished.

These two Matz brought to my attention:

>   * assigning NULL to integer is wrong,
>   * // is not valid for all compilers,

Both have been repaired and will be in my next checkin.

>   * some complier cannot recognize escape sequence like as \e,

Yes, I thought it might be so.  I will put them in hex, okay?

>   * some functions which defined to return VALUE don't return any values,

Yes, a few of the methods in Syck::Loader I believe.  Fixed.  Thank you.

>   * ANSI function definitions/prototypes may cause a problem
>     with some old compilers, and

I will spend time tomorrow converting these as well.

>   * not only tool-generated files, should there be source files?

I use Yacc (gram.y -> gram.c) and re2c (token.re -> token.c, implicit.re
-> implicit.c).  I can certainly include source files for these, but
likely we don't want a re2c dependancy.  Should I leverage yacc since
it's already used for Ruby's grammar?

_why


In This Thread

Prev Next