DrForr

Yesterday I thought I might see whether Dancer2 could survive running inside Inline::Perl5 as a possible migration scheme. Roughly 100 of 120 files ran cleanly after wrapping them inside a perl6 heredoc, and as of 10:30pm I've only 6 files left to fix. The majority of the changes have been adding 't/' to the Dancer2 file paths as it apparently relies on FindBin, which reports a different location since I'm running test suites inside perl5 from inside perl6. The other changes have been caller() related which I'm skipping for the time being, and two files where it can't find the correct configuration location, again probably due to the nested interpreters.

I figure I can't go too far wrong with a test suite as extensive as Dancer2's, and yes, I do have an ulterior motive here, wanting to expose the interpreter to a different sort of load. At least this way I can migrate code piecewise and at the same time stress Inline::Perl5 in exciting and new ways.