dynamic - .NET 4 makes for better unit testing/mocking due to the ability to monkey patch? -
Consider this about the implementation that comes up.
In theory, will this allow the monkey to correct the bar? Good or bad, it does not matter what the dynamic keywords will allow, (looking at someone else's non-testable code) (at least with ease)? If it is reading for C # and VB, then there are many possibilities in it.
What are the views on this?
Dynamic type support in .NET 4 You do not actually have full monkey-patching support in the CLR type system gives. This gives you another way to mimic the object, but it is very good to be clear in the present way (see Mock:)
With dynamic types, you lose intensities, so logic It can be given that this advice is not given for the joke to be dynamic.
Iron Python style prevention will allow you to wrap an existing object with your desired behavior, but it will not allow you to tell the framework to patch all the foo objects after the point) Then the bar will call Bar 2 instead of the method bar.
Keep in mind, there are 2 different types of systems in play with IronRuby and IronPython, the built-in CLR type system and IronRuby / IronPython type system, when they call the C # code there Going is marshaling. Even if Irony / Ironpathas can properly approve monkey patches in their own type of system, they can not use the same mechanism to patch the CLRs type system.
If you want monkey patching then you need proper intervention and it is hard :
Comments
Post a Comment