Sawyer X

No reason it was exactly 100. I just wanted something that didn't take very long. Let's raise and try to fix any problem we see.

I tested with 1,000 for both `burn_in` and `calls` and then I can reproduce the failure: ``` $ perl -Mblib -Ilib t/leak-pointer.t 1..2 ok 1 - use Audio::Chromaprint; not ok...

This doesn't seem to happen every time I run the test. I'm not sure why it's sporadic.

Good point! Will change that soon.

When I change it to `gv_stashsv`, all the tests fail and it can't load it. Also, I don't understand the comment on `strlen`.

That is pretty cool. Thank you so much for the explanation of strings and nulls in packages. I can't find a way to incorporate that into the tutorial (feel free...

You note that while we can prevent `autodoc.pl` from appearing the documentation list by indenting the POD inside it, still won't prevent the POD from being rendered and I'm confused...

Oh, I see. So we need two changes: * Create documentation for perlapi. We can do that, even if all it explains is what it does and says these are...

The `PERL_UNICODE=SDL` maybe, but why would you set the `DANCER_CONTENT_TYPE` globally when running tests? Is it something you set per user?

I'm sorry. I have to go with the slippery slope defense here. Do we need to now defend all of our testing code from someone tempring with run-time environment variables?...