Should a binding module support multiple Node versions

[Liam]

My first draft of the Xapian binding was for 0.4. It's about to get
some more work, including a port to 0.6 and testing on 0.7. Should I
plan to support 0.4, 0.6, and 0.7/8, and if so, are there node_version
header defines for use with #ifdef?

[Nathan Rajlich]

You can support as far back as is practical for you. I don't think people are caring about v0.4.x so much these days, but I did make a shim for eio_custom()/uv_queue_work(): https://gist.github.com/1368935.

Also, you can check out that gist as well to see how node_version.h can be used with #if to conditionally do things.

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[christkv]

there are still tons off people using 0.4 which is somewhat annoying
and I assume it will get a lot worse as 0.8 comes out. I plan on only
supporting current version + last. so once 0.8 is out the mongodb
driver will stop support for 0.4.X actively.

[Liam]

There have been 15 bugfix releases for 0.6 in 5 months. That might
have affected migration somewhat.