Log in

No account? Create an account

Previous Entry | Next Entry

Ruby's binding to Redland is maddeningly hopeless, but I did get this out of it with a SPARQL query...

aredridel@mizar:~$ ruby rdfq.rb file://$(pwd)/dc.rdf
Function rasqal_query_get_source_sequence is deprecated - use rasqal_query_get_data_graph_sequenceCalling deprecated rasqal_triples_source factory method new_triples_match (will go in rasqal 0.9.10+) {"title"=>#<SWIG::TYPE_p_librdf_node:0x40078cb4>, "x"=>#<SWIG::TYPE_p_librdf_node:0x40078d04>}

Let's just leave it that I have major issues with SWIG.


( 2 comments — Leave a comment )
May. 29th, 2005 05:06 am (UTC)
Ruby binding complex? Hey, I'm not a ruby user
I just take patches for ruby apis to redland, so it's whatever the last person sent me.
Yes SWIG can get in the way. I've heard ruby can talk directly to C so maybe something a
better can be done with that method, but it's not going to be written by me.

Re: that warning message, it'll go in redland 1.0.1 which is pretty much ready to ship.


Dave Beckett
May. 29th, 2005 07:02 am (UTC)
Re: Ruby binding complex? Hey, I'm not a ruby user
Alrighty -- In that case I may be sending patches against redland-bindings to improve the Ruby API. Ruby can talk straight to C, definitely (both inlined C with an addon package, and its own native extension method)

I've been playing with redland off and on, so it'd be really nice to have it bound to my favorite language.
( 2 comments — Leave a comment )