http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/ Tony Perrie's Weblog Tue, 15 May 2012 22:43:17 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/comment-page-1/#comment-361834 john Furst Thu, 08 Apr 2010 02:31:19 +0000 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/#comment-361834 can i see the c++ header file please. :) can i see the c++ header file please. :)

]]> http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/comment-page-1/#comment-160525 BSE Sun, 13 Jul 2008 04:22:40 +0000 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/#comment-160525 Google sent me here when I asked it for help with a problem in erlang. The person of small stature driving the chess automaton known as Google is truly wise, for this post helped solve the problem. Google sent me here when I asked it for help with a problem in erlang. The person of small stature driving the chess automaton known as Google is truly wise, for this post helped solve the problem.

]]> http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/comment-page-1/#comment-70 Administrator Mon, 03 Apr 2006 22:54:46 +0000 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/#comment-70 Right on, brother. Thanks for catching that one. Right on, brother. Thanks for catching that one.

]]> http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/comment-page-1/#comment-69 Phillip Bogle Mon, 03 Apr 2006 22:48:26 +0000 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/#comment-69 Is that $gt; intended to be a ">"? I haven't tried the code yet but ">" makes more sense to me. Is that $gt; intended to be a “>”? I haven’t tried the code yet but “>” makes more sense to me.

]]> http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/comment-page-1/#comment-55 Administrator Fri, 24 Mar 2006 18:59:31 +0000 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/#comment-55 Indeed. I think perhaps maybe I was going to do some kind of error check in that function *eventually* before I rewrote it in ruby and activerecord. Indeed. I think perhaps maybe I was going to do some kind of error check in that function *eventually* before I rewrote it in ruby and activerecord.

]]> http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/comment-page-1/#comment-54 Mulekick Fri, 24 Mar 2006 15:48:06 +0000 http://involution.com/2006/03/20/rss-parser-in-10-lines-of-ruby-or-in-153-lines-of-c/#comment-54 You could make the c++ function "int feed_parser::get_tag(string& sOutput, istream* input)" into a void and remove the "return 0;" line. You don't use the return value from this function anyhow. You could make the c++ function “int feed_parser::get_tag(string& sOutput, istream* input)” into a void and remove the “return 0;” line. You don’t use the return value from this function anyhow.

]]>