Comments on: Operator overloading your domain model with interfaces and base classes http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/ Thoughts on life, liberty, and information technology Tue, 24 Jan 2012 10:43:34 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: brian http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93903 brian Thu, 21 Feb 2008 14:15:41 +0000 http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93903 Hey, I like comment spam when it's not spam. :) The generic of EntityBase<T> requires T to be the entity type, which is why I made FieldingStats<T> generic in the first place -- so it can pass the type to the underlying EntityBase<T>. So it looks like this: public class GameFieldingStats : FieldingStats<GameFieldingStats> { } public class FieldingStats<T> : EntityBase<T>, IFieldingStats where T : FieldingStats<T>, new() public class EntityBase<T> : ActiveRecordBase<T>, IEquatable<T> where T : ActiveRecordBase<T> whew! Hey, I like comment spam when it’s not spam. :)

The generic of EntityBase<T> requires T to be the entity type, which is why I made FieldingStats<T> generic in the first place — so it can pass the type to the underlying EntityBase<T>.

So it looks like this:

public class GameFieldingStats : FieldingStats<GameFieldingStats> { }
public class FieldingStats<T> : EntityBase<T>, IFieldingStats where T : FieldingStats<T>, new()
public class EntityBase<T> : ActiveRecordBase<T>, IEquatable<T> where T : ActiveRecordBase<T>

whew!

]]> By: Lucas http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93530 Lucas Thu, 21 Feb 2008 03:37:54 +0000 http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93530 *sigh* public class Person : EntityBase { } is public class Person : EntityBase<Address> { } i hope you just edit the original and delete all this spam :) *sigh*
public class Person : EntityBase { }
is
public class Person : EntityBase<Address> { }

i hope you just edit the original and delete all this spam :)

]]> By: Lucas http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93528 Lucas Thu, 21 Feb 2008 03:35:14 +0000 http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93528 ugh! the generic parameters got chopped replace EntityBase with EntityBase<T> ugh! the generic parameters got chopped
replace EntityBase with EntityBase<T>

]]> By: Lucas http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93523 Lucas Thu, 21 Feb 2008 03:33:13 +0000 http://www.sidesofmarch.com/index.php/archive/2008/02/20/operator-overloading-your-domain-model-with-interfaces-and-base-classes/#comment-93523 hi brian! i'm writing this from my rooftop watching the lunar eclipse... don't forget to use this restriction public abstract class EntityBase where T : EntityBase {} this makes sure that T can only be a class which inherits EntityBase so you can't do something wierd like: public class Person : EntityBase { } // WTF? (disclaimer: not looking at code right now, might have syntax errors) hi brian! i’m writing this from my rooftop watching the lunar eclipse…
don’t forget to use this restriction

public abstract class EntityBase
where T : EntityBase {}

this makes sure that T can only be a class which inherits EntityBase so you can’t do something wierd like:

public class Person : EntityBase { } // WTF?

(disclaimer: not looking at code right now, might have syntax errors)

]]>