comment on

Sorry I can't contribute to your questions, but I find your strategy interesting.

( and its a meditation, after all :)

> So, I have 50000+ tests that I want to PASS (ideally)

Not sure if I understood correctly but are you saying you started with porting the test code first?

Wouldn't it be wiser to try to test your P6 code (in case of same functionality and semantic) with your P5 test suite (using a kind of bridge maybe)? Like this keeping both test-suites in sync?

I understand that type checking doesn't make sense and that you could drop this part of the tests, but the risk of bugs in the test-suite would be reduced and you could immediately start porting.

OTOH are test-suites easier to translate because they mostly consist of "simpler" code, which could help you having a smoother transition phase. (maybe?)

Cheers Rolf

PS: Je suis Charlie!

In reply to Re: Porting (old) code to something else by LanX
in thread Porting (old) code to something else by Tux

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.


We don't bite newbies here... much
	PerlMonks