Skip to content

Commit

Permalink
Version bump and readme update
Browse files Browse the repository at this point in the history
  • Loading branch information
soulcutter committed Apr 1, 2014
1 parent ab6631a commit 482803a
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 1 deletion.
11 changes: 11 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,17 @@ Why not DOM parsing?
> DOM parsers load the entire document into memory. Saxerator only holds a single chunk in memory at a time. If your
> document is very large, this can be an important consideration.
When I fetch a tag that has one or more elements, sometimes I get an `Array`, and other times I get a `Hash` or `String`
- how can I treat these consistently?

> You can treat objects consistently as arrays using
> [Ruby's built-in array conversion method](http://www.ruby-doc.org/core-2.1.1/Kernel.html#method-i-Array)
> in the form `Array(element_or_array)`
>
> Generally you should not need to convert a parsed element to a `String` or `Hash`. One case it
> occasionally comes up is for elements that are sometimes-empty. Empty elements behave mostly like an
> empty `Hash`, however you may convert it to a more `String`-like object via `#to_s`
### Acknowledgements ###
Saxerator was inspired by - but not affiliated with - [nori](https://github.com/savonrb/nori) and [Gregory Brown](http://majesticseacreature.com/)'s
[Practicing Ruby](http://practicingruby.com/)
Expand Down
2 changes: 1 addition & 1 deletion lib/saxerator/version.rb
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
module Saxerator
VERSION = "0.9.2"
VERSION = "0.9.3"
end

0 comments on commit 482803a

Please sign in to comment.