my face
About Me

Published Posts

All Posts

New Post


View by Tag:

interviewing, code, testing, philosophy, blog, wantmyjob, virtualization, railsmud, heroku, ruby, published, neoarchaeology, railsgame, rails, juggernaut, astrino, cheaptoad, shannaspizza, mongodb, refactorit, devise, rvm, passenger, jruby, programming, vagrant, chef, railsframe, business, codefolio


Online Portfolio

Resume

Profile on LinkedIn

Recommend me on WorkingWithRails: Recommend Me

Catch-up post for last week

Posted: 2 years ago (2009-06-29 16:11:02 UTC )

I find that even when I'm doing geeky stuff, I don't always get around to posting about it on the weekend. Last week, in addition to the five posts I managed, I also screwed around with SWIG and Ruby. My big insight, such as it is, is that interfaces with function pointers are going to be hard here.

It seems like (and I haven't tested this) the right answer is going to be keeping an internal variable pointing to a proc, and having an extra function pointer in the Ruby binding that I can set, which calls that internal proc. So basically, a little hand-written mapping function.

It would be nice if SWIG could do that for itself, of course. But it looks like it currently doesn't, which makes its default Ruby interfaces much less useful.

Previous: will_paginate example CSS / Next: Hm. Basically done?

Edit | Destroy | See All Posts

blog comments powered by Disqus