Mr. Tiwari: Major ports are rather like major rewrites, in that if you think of the program as a tree, the parts that stay the same are the trunk and branches, and the parts that change are the leaves.
If you draw a picture of the old program on a whiteboard, you have an (initial) design for the new program. If the calls and parameters look like a reasonably good API, you can start by writing *mock leaves*, which will help you understand both the program and the new language. it should pass your integration tests, albeit with fake data. Then start filling in the low-level details, starting with the *last* step and working backwards. Each time you break something, your tests will tell you, and you can fix it quickly. In a previous life, this and some elegant tooling allowed my employer to make a profit off doing fixed-price ports. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
