From mboxrd@z Thu Jan  1 00:00:00 1970
From: wmorgan-sup@masanjin.net (William Morgan)
Date: Wed, 01 Jul 2009 11:11:37 -0700
Subject: [sup-talk] Sup on Ruby-1.9
In-Reply-To: <1246461780-sup-5146@cannonball>
References: <1246461780-sup-5146@cannonball>
Message-ID: <1246471261-sup-3755@entry>

Reformatted excerpts from Ingmar Vanhassel's message of 2009-07-01:
> Has anyone been keeping a TODO list for running sup on ruby-1.9?

The major blocker for a while was the Ferret gem. With the advent of the
Xapian branch, I have been toying around with getting Sup + Xapian to
work on 1.9.1. So far all the gem dependencies seem to compile except
ncurses, which needs some minor code tweaks.

The latest Xapian has Ruby 1.9.1-compatible bindings, but unfortunately
the API seems to have shifted since Rich's patches. I get:

  lib/sup/xapian_index.rb:24:in `initialize': Wrong arguments for overloaded method 'WritableDatabase.new'. (ArgumentError)
  Possible C/C++ prototypes are:
      WritableDatabase.new()
      WritableDatabase.new(std::string const &path, int action)
      WritableDatabase.new(Xapian::WritableDatabase const &other)
    from lib/sup/xapian_index.rb:24:in `new'
    from lib/sup/xapian_index.rb:24:in `initialize'
    from bin/sup:132:in `new'
    from bin/sup:132:in `<module:Redwood>'
    from bin/sup:62:in `<main>'

Moving to 1.9 is highly desirable. It would be a major win for non-ASCII
display issues and for speed in general. I would also like to try moving
some of the display code from threads to fibers, since there are still
weird threading bugs in there that occasionally crop up, and I think it
would simplify the implementation.
-- 
William <wmorgan-sup at masanjin.net>