Seeing as FIT has a Perl fixture, why not just use FIT?

That'd be the FIT port that I did, which was complete in early days, and served to shake out some issues in FIT early on, but hasn't been touched since, largely due to lack of interest on the part of anyone in the Perl community at the time. (I prefer to work on stuff that gets used. There weren't takers then; there might be now.)

I'd rate my port as being better than "proof of concept", and probably good enough to base work on if you're willing to roll up your sleeves, but it's not anywhere near current.

Ingy did another port, (the one on CPAN), shortly thereafter. I don't know if he's kept his updated, either.

There's been some backchannel discussion about getting the Perl port updated for FIT 1.1. If anyone is seriously interested (say, in helping out), /msg me.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.