From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Sup on Ruby-1.9
Date: Wed, 01 Jul 2009 11:11:37 -0700 [thread overview]
Message-ID: <1246471261-sup-3755@entry> (raw)
In-Reply-To: <1246461780-sup-5146@cannonball>
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>
next prev parent reply other threads:[~2009-07-01 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 15:29 Ingmar Vanhassel
2009-07-01 18:11 ` William Morgan [this message]
2009-07-01 19:15 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1246471261-sup-3755@entry \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox