sup talk - Jul 2009 - Sup on Ruby-1.9

Has anyone been keeping a TODO list for running sup on ruby-1.9?

I haven''t had the time to try it myself, but I''d like to have
a rough
idea of what I''m looking at.

-- 
Exherbo KDE, X.org maintainer

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>

Reformatted excerpts from William Morgan''s message of
2009-07-01:
> The latest Xapian has Ruby 1.9.1-compatible bindings, but unfortunately
> the API seems to have shifted since Rich''s patches.
Hm, AFAIK that isn''t an API change. Maybe I compiled my Xapian bindings
wrong somehow. Or something.
-- 
William <wmorgan-sup at masanjin.net>