|
|
|
|
|
by koyote
2092 days ago
|
|
While I agree, I feel that third-party library consumption is a bit of an edge case (i.e. the majority of your interface implementations won't be wrappers around third-party stuff). Whenever I do work closely with a third-party library, the wrapping pays for itself quite quickly because it never takes long for you to find a 'quirkiness' or unsuitability in how the library implements something and you end up with code resembling this: public void Do() {
_instance.SpecialOptionForTheBehaviourYouRequire = true;
try
{
_instance.Do();
}
catch
{
// Workaround for bug that has not been fixed in ThirdParty Library yet. Remove when fixed!
_instance.ResetBrokenStateCausedByBug();
_instance.Do();
}
}
|
|