Permalink
Browse files

Merge pull request #36 from Gazler/gh-pages

Update broken URLs on C Extension guide.
  • Loading branch information...
sferik committed Nov 24, 2012
2 parents b2d42eb + ec7d8c8 commit 3c6b34208e222dafb585ea6fea754fecb2f16e25
Showing with 4 additions and 4 deletions.
  1. +4 −4 c-extensions.md
View
@@ -336,9 +336,9 @@ Wrapping Existing Libraries
A common reason for writing a C extension is to wrap an existing C or C++
library. This can be done manually (see this tutorial --
[part
-1](http://tenderlovemaking.com/2009/12/18/writing-ruby-c-extensions-part-1)
+1](http://tenderlovemaking.com/2009/12/18/writing-ruby-c-extensions-part-1.html)
and [part
-2](http://tenderlovemaking.com/2010/12/11/writing-ruby-c-extensions-part-2)),
+2](http://tenderlovemaking.com/2010/12/11/writing-ruby-c-extensions-part-2.html)),
but several tools also exist:
* [SWIG](http://www.swig.org/), the Simplified Wrapper Interface Generator, is
@@ -365,8 +365,8 @@ References
This guide is based largely on this excellent two-part tutorial:
-* [part 1](http://tenderlovemaking.com/2009/12/18/writing-ruby-c-extensions-part-1)
-* [part 2](http://tenderlovemaking.com/2010/12/11/writing-ruby-c-extensions-part-2)
+* [part 1](http://tenderlovemaking.com/2009/12/18/writing-ruby-c-extensions-part-1.html)
+* [part 2](http://tenderlovemaking.com/2010/12/11/writing-ruby-c-extensions-part-2.html)
The main references for ruby's C API are:

0 comments on commit 3c6b342

Please sign in to comment.