[#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: YAML problem

From: why the lucky stiff <ruby-core@...>
Date: 2003-05-23 15:04:43 UTC
List: ruby-core #1073
NAKAMURA, Hiroshi (nahi@keynauts.com) wrote:
> 
> Don't take that too much.  YAML.rb should not depend Ruby's
> type and object to the extent possible for interoperability
> and easy editing.  I don't think YAML is for typed object
> marshalling format.
> 

I just want YAML.rb to be on its best behavior with Ruby.  If a User has
an Exception instance in a data structure, I'd like it to the best it
can with that Exception.

If I were lazy, YAML.rb would just make a:

  --- !ruby/object:Exception {}

But with some understanding of the Exception class, we get:

  --- !ruby/exception
  message: 'Parse error in line 12, col 3'

Which is useful for error logs.  That's my reasoning behind meeting much
of the Marshal::UT.

_why

In This Thread