Well, when the problem domain is XML, I have to admit I tend to look for the simplest solution. There are so many different XML parsers and writers, and many have subtle issues with reading/writing XML from other parsers/writers. So, in this case, I had the XML serialization already done in perl, and decided that since this will be called once a month in my ruby application to just "use perl;" I am definitely a pragmatist more than a purist.
Chris On 7/17/06, Ben Bleything <[EMAIL PROTECTED]> wrote:
On Mon, Jul 17, 2006, Ben Matasar wrote: > I realize you guys are joking, but I'm sure the work Chris actually > needs to do is in perl, and it's not a one liner. I have a piece of > code that needs to call Geo-Coder-US [1] as part of a larger app, and > reimplmenting that in ruby is outside the scope of my project ;). I am and I'm not. There aren't really all that many *common* tasks that you can't do in Ruby. And I would suggest that if you're having to shell out to another script that perhaps it might be time to rethink your application design. If it truly is more complex, then let's see an example or get more details. Obviously the code he sent was fake, but I'd like to know what the real problem is so we can see if there might be a way to avoid a dangerous shell operation. > CPAN is your friend. So is rubyforge. http://geocoder.rubyforge.org/ :) Ben _______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
_______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
