Re: Design Question - multiple XML parsers/ dependencies
Robert Klemme <[email protected]>
| Newsgroups | gmane.comp.lang.ruby.general |
|---|---|
| Message-ID | <CAM9pMnP7khagVe23PVgwLjTB_=AtGMPZzDa_ufzxshxoSESFRQ@mail.gmail.com> |
On Sun, Mar 31, 2019 at 11:54 AM Gerald Bauer <[email protected]> wrote: > See the multi_xml [1] and multi_json [2] for some "real world" > examples with sources [1a][2a]. > [1] https://rubygems.org/gems/multi_xml > [2] https://rubygems.org/gems/multi_json > [1a] https://github.com/sferik/multi_xml > [2a] https://github.com/intridea/multi_json I am always a bit skeptical about these approaches (i.e. providing a general wrapper) because you either have to agree on the least common denominator of features or have to implement features in the wrapping layer. In any case the wrapping layer needs to be updated whenever one of the backend changes, which potentially creates a lot of maintenance effort. Also, especially with REXML in the mix I believe that had some quirks related to encodings in the past. So generally testing effort will be quite high. My 0.02€. If only a few operations are used then the situation might look different. Still you add one dimension to the test matrix because you have to test all target system configuration combinations. Kind regards robert -- [guy, jim, charlie].each {|him| remember.him do |as, often| as.you_can - without end} http://blog.rubybestpractices.com/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>