Databases
StackOverflow2013
Postsdbo
POWhere do I place common logic required in multiple classes implementing the same interface?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhere do I place common logic required in multiple classes implementing the same interface?
    primarykey
    data
    text
    <p>Given the following interface:</p> <pre><code>public interface IFoo { bool Foo(Person a, Person b); } </code></pre> <p>and the following two implementations of the above:</p> <pre><code>public class KungFoo : IFoo { public bool Foo(Person a, Person b) { if (a.IsAmateur || b.IsAmateur) // common logic return true; return false; } } public class KongFoo : IFoo { public bool Foo(Person a, Person b) { if (a.IsAmateur || b.IsAmateur) // common logic return false; return true; } } </code></pre> <p>where should I place the "common logic" (as commented in the code) so it is in just one place (e.g. as a Func) and does not need to be repeated (as is the case above) for multiple implementations?</p> <p><em>Note that the example above is very trivial but the real-life "common logic" is more complicated and the Foo() method does something useful!</em></p> <p>I hope the question is clear (and not already been answered elsewhere - I did do a search) but feel free to probe me for more details if required.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USAppulus
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhere do I place common logic required in multiple classes implementing the same interface?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhere do I place common logic required in multiple classes implementing the same interface?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COLooks like there's a very similar question here: http://stackoverflow.com/questions/5343923/where-to-put-common-interface-methods-when-dealing-with-partial-classes-inherit - only saw it in the Related section after I posted this one! Although mine is when two methods do different things but have common logic embedded within them...
      singulars
      1. POWhere do I place common logic required in multiple classes implementing the same interface?
      1. USAppulus
    2. COIt's a bit unclear what specifically you're deeming common logic here. You're indicating a line of code that doesn't refer to the properties of the class at all so it could just be factored out into a static method in some utility class. If your common code uses the class members you may be able to use an extension method, but only if these members are exposed by the interface. Finally you could use a base class. But the 'right' answer depends somewhat on the specifics of the common logic.
      singulars
      1. POWhere do I place common logic required in multiple classes implementing the same interface?
      1. USJames Gaunt
    3. CO@James: thanks for your comment. Sorry, my mistake: I made the common logic too simplistic but a and b are objects of two different types/classes which do not belong to the implementation classes. So, based on your comment, it should probably be placed in a static method in a utility class.
      singulars
      1. POWhere do I place common logic required in multiple classes implementing the same interface?
      1. USAppulus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload