A. Agree that killing the backward compatibility is a must. All new development should go with new syntax.
B. On the other hand, how about the evolving project with tons of existing tests using the old syntax? Must it stuck with old syntax forever or totally rewrite all tests? I hope there is a better option would allow me to keep the old tests as is and use new syntax in new test cases being added to project. Maybe I can use 3.6 and 4.0 side by side just like I can have NMock (real old test cases) and Rhino.Mocks side by side in one project. How about a completely new namespace for 4.0? Rhino.Fakes is what I somebody who lack of imagination, can think about. Cheers, Kenneth --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en -~----------~----~----~----~------~----~------~--~---
