HN Explorer

9 comments

[ 3.5 ms ] story [ 21.8 ms ] thread
flogic
This is one of the most awesome thing's I've ever seen. I guess it would be a bad idea to use it for production code... Too bad though.
berntb
Am I missing something?

My C days was a long time ago, but this looks like simple and elegant stuff to me. What would be the problem with production code? The Go language?

bradfitz
I think it might have a bug or two yet. Perl is reference counted and Go is garbage collected. Keeping those two synchronized was a bit tricky and I still fear I messed it up somewhere... I need to re-read the Perl docs on when I'm supposed to up & down the Perl refcounts.
rbanffy
There's no better way to find the bugs than to use the code in production ;-)

It was a great talk, BTW.

flogic
Perl's behind the scenes C code is rather gnarly. Trusting a new tool to get it right the first time is a bit much. Once I'm comfortable it's had some time to age properly, I'd be more than willing to deploy it.
jrockway
Sounds useful, and campher.c looks like a piece of code that should be easy to repurpose for writing bindings to Perl in other languages.