[Dan]>> ... Honestly I'd prefer just a single executable, named [Dan]>> parrot
I would totally dig that. I use imcc for everything; why not just call it "parrot" :-)
Why don't we just build a single executable, where the main c-source isn't called test_main.c but parrot.c and the executable is parrot$EXE, so what ;-)
I said, I'd prefer some additional tinderboxen results first, but as imcc runs all tests on Win32 too, we could jump into the cold water (which doesn't seem to be really deep anymore) instantly and just update Makefile and the test scripts. Its all in place.
Just replace the env that runs now: $ IMCC=imcc perl t/harness t/o*/ma*.t with parrot.
[Dan]>> Dan > Luke leo, tried to reconstruct quotes for clarity.
