view api/Objects/InvalidContainershipException.cs @ 161:81abc04b3dbe

Re #192: Improve "clean coding" practice * Move some calculation methods for equipment out of the encapsulation objects
author IBBoard <dev@ibboard.co.uk>
date Sun, 04 Oct 2009 12:00:16 +0000
parents 2f3cafb69799
children ece26f6a62f3
line wrap: on
line source

//  This file (InvalidContainershipException.cs) is a part of the IBBoard.WarFoundry.API project and is copyright 2009 IBBoard
// 
// The file and the library/program it is in are licensed and distributed, without warranty, under the GNU Affero GPL license, either version 3 of the License or (at your option) any later version. Please see COPYING for more information and the full license.

using System;

namespace IBBoard.WarFoundry.API.Objects
{
	/// <summary>
	/// A custom exception for when a unit was added as a sub-unit of another unit, but was not of a <see cref=" UnitType"/> that can be contained
	/// by that unit.
	/// </summary>
	public class InvalidContainershipException : Exception
	{
		private Unit containing;
		private Unit contained;
		
		public InvalidContainershipException(Unit containingUnit, Unit containedUnit) : base(CreateMessageString(containingUnit, containedUnit))
		{
			containing = containingUnit;
			contained = containedUnit;
		}
		
		private static string CreateMessageString(Unit containingUnit, Unit containedUnit)
		{
			return containingUnit.Name+" cannot contain "+containedUnit.Name+" because units of "+containingUnit.UnitType.Name+" cannot contain units of "+containedUnit.UnitType.Name;
		}
		
		/// <value>
		/// The <see cref=" Unit"/> that the contained unit was added to
		/// </value>
		public Unit ContainingUnit
		{
			get { return containing; }
		}
		
		/// <value>
		/// The <see cref=" Unit"/> that was added as a contained unit, but which was not of an allowed type
		/// </value>
		public Unit ContainedUnit
		{
			get { return contained; }
		}
	}
}