Added support to YAML.quick_emit to be called on nested objects where
the
same emitter needs to be flowed through
Array.pack(“a”) was not dealing with nil input
yaml.rb should to “require stringio” like MRI does
Deleted a second copy of yaml.rb from the IronRuby.Libraries.Yaml folder
Added MutableString.Dump property to be able to inspect large strings in
VS.
ir.exe -X:ExceptionDetail was not working in interactive mode because
ir.exe catches the exception and does not call
RubyExceptionData.SetCompiledTrace like a rescue block in Ruby code
would
do. Fixed this
o Have we checked that not being a subclass of YAML::Syck::Map is ok?
I suspect it is an implementation detail, but I want to check. If it is
implementation detail, then we probably don’t need to spec that one.
From: Shri B.
Sent: Friday, March 13, 2009 3:41 PM
To: IronRuby External Code R.
Cc: [email protected]
Subject: FYI review: YAML improvements
Tomas has reviewed this.
Added support to YAML.quick_emit to be called on nested objects where
the
same emitter needs to be flowed through
Array.pack(“a”) was not dealing with nil input
yaml.rb should to “require stringio” like MRI does
Deleted a second copy of yaml.rb from the IronRuby.Libraries.Yaml folder
Added MutableString.Dump property to be able to inspect large strings in
VS.
ir.exe -X:ExceptionDetail was not working in interactive mode because
ir.exe catches the exception and does not call
RubyExceptionData.SetCompiledTrace like a rescue block in Ruby code
would
do. Fixed this
FYI: After talking with Brian from RubySpec, I have pulled the specs
that check for be_kind_of(YAML::Syck::*). We have decided that it is
implementation detail, and since IronRuby and RbYaml don’t support it,
it isn’t something that should be specced.
JD
From: Jim D.
Sent: Friday, March 13, 2009 11:13 PM
To: Jim D.; Shri B.; IronRuby External Code R.
Cc: [email protected]
Subject: RE: FYI review: YAML improvements
o Have we checked that not being a subclass of YAML::Syck::Map is ok?
I suspect it is an implementation detail, but I want to check. If it is
implementation detail, then we probably don’t need to spec that one.
Zlib::GzipWriter.wrap(@io) do |gz|
From: Shri B.
Sent: Friday, March 13, 2009 3:41 PM
To: IronRuby External Code R.
Cc: [email protected]
Subject: FYI review: YAML improvements
Tomas has reviewed this.
Added support to YAML.quick_emit to be called on nested objects where
the
same emitter needs to be flowed through
Array.pack(“a”) was not dealing with nil input
yaml.rb should to “require stringio” like MRI does
Deleted a second copy of yaml.rb from the IronRuby.Libraries.Yaml folder
Added MutableString.Dump property to be able to inspect large strings in
VS.
ir.exe -X:ExceptionDetail was not working in interactive mode because
ir.exe catches the exception and does not call
RubyExceptionData.SetCompiledTrace like a rescue block in Ruby code
would
do. Fixed this
o Have we checked that not being a subclass of YAML::Syck::Map is ok?
I suspect it is an implementation detail, but I want to check. If it is
implementation detail, then we probably don’t need to spec that one.
From: Shri B.
Sent: Friday, March 13, 2009 3:41 PM
To: IronRuby External Code R.
Cc: [email protected]
Subject: FYI review: YAML improvements
Tomas has reviewed this.
Added support to YAML.quick_emit to be called on nested objects where
the
same emitter needs to be flowed through
Array.pack(“a”) was not dealing with nil input
yaml.rb should to “require stringio” like MRI does
Deleted a second copy of yaml.rb from the IronRuby.Libraries.Yaml folder
Added MutableString.Dump property to be able to inspect large strings in
VS.
ir.exe -X:ExceptionDetail was not working in interactive mode because
ir.exe catches the exception and does not call
RubyExceptionData.SetCompiledTrace like a rescue block in Ruby code
would
do. Fixed this
Thanks,
Shri
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.