| Age | Commit message (Collapse) | Author |
|---|
|
The only remaining use of this function was to get the internal
message object from an exception's hidden `mesg` instance
variable to allow it to be dumped wiithout converting to a string.
As discussed in #103, this exposes internal implementation details
of CRuby, and ultimately does not provide any real utility to the
user since they can't directly inspect this hidden variable. The
test change here is to reflect CRuby behavior that denies equality
if the internal message objects do not match, as is the case after
the exception has been loaded and now has a simple String value.
The impact to users is that exceptions with special hidden message
objects will convert those objects to String during marshaling
through YAML. I believe this only affects NameError and its
descendants, since users can't set this field directly on their
own exception types.
Fixes #103.
|
|
Fixes #428
|
|
|
|
|
|
|
|
|
|
This will be released in Psych 3.0.3. See #352.
|
|
|
|
Add Psych::Handler#event_location
|
|
set the encoding to UTF-8 and hope for the best. This appears to be how
libyaml works.
This issue was noticed in yaml/store because it extends pstore which will
create an IO in read_only mode as:
```ruby
RD_ACCESS = {mode: IO::RDONLY | IO::BINARY, encoding: Encoding::ASCII_8BIT}
```
The data in the test case I was debugging was in fact UTF-8 data and MRI was
happy to take this 8bit IO and pretend it is UTF-8. Form-fitting ftw.
|
|
This adds a new reported event to Psych::Handler, event_location, with precise start/end line/column information.
The line/column information provided by Psych::Parser#mark is not very useful because it points to the location past the event.
|
|
Fixes #319.
|
|
Not sure why snakeyaml doesn't follow libyaml here. I'll follow
up with them.
|
|
146a637e2205b2b36a6fa83fc0c6f7ce0c74e123."
This reverts commit f5455216532f33e2b32bb035d14d820d1d37906b.
|
|
|
|
I had to hard-code two places that referenced a constant under
Psych because neither the Rakefile nor a "gem build" loads that
file. It was picking up the older version in my current JRuby
process.
|
|
|
|
|
|
Fixes jruby/jruby#2901.
|
|
use maven to resolve jar dependencies for compilation. setup jar-dependencies
to install the snakeyaml jar when installing the gem via rubygems or bundler.
added java code to reflect the snakeyaml vesion which got finally loaded into
the jruby-classloader.
|
|
|
|
|
|
|
|
|
|
|
