AngouriMath

Navigation

Home Quick start Wiki Almanac Research What's new Try Use Angouri.org GitHub Report a bug Donate Contacts

AngouriMath.Core.Exceptions

← Back to list of namespaces

Classes within the AngouriMath.Core.Exceptions namespace

• AngouriBugException

  Summary

  If one was thrown, the exception is probably not foreseen by AM. Report it is an issue

• AngouriMathBaseException

  Summary

  This is the base exception of all exceptions thrown by AngouriMath.
  If one needs to catch all exceptions from AngouriMath, it is enough
  to catch this one
  

• BadMatrixShapeException

  Summary

  Happens when matrices don't have a correct shape, e. g.
  trying to concat when they have different sizes by one side.
  

• CannotEvalException

  Summary

  Is thrown when something cannot be collapsed into a single number or boolean

• CannotParseInstanceException

  Summary

  May be thrown when trying to parse an instance from a string
  

  Example

  Set set = "{ 1, 2 }"; // not thrown
  Set set = "1 + 2"; // thrown

• ElementInSetAmbiguousException

  Summary

  Cannot figure out whether the entity is in the set

• FunctionArgumentCountException

  Summary

  Thrown when a wrong number of arguments are encountered when parsing a function
  from a string.
  

• FutureReleaseException

  Summary

  Is thrown when the requested feature is still under developing
  or not considered to be developed at all
  

• InvalidArgumentParseException

  Summary

  Thrown when an invalid argument passed to a AM's function

• InvalidMatrixOperationException

  Summary

  Thrown in matrix operations
  

• InvalidNumberException

  Summary

  Thrown when an invalid number is passed as an argument

• InvalidNumericSystemException

  Summary

  Occurs when an invalid numeric system was provided to functions
  ToBaseN(AngouriMath.Entity.Number.Real,System.Int32) or FromBaseN(System.String,System.Int32)

• InvalidProtocolProvided

  Summary

  Occurs when no custom compilation protocol was provided, while the built-in one
  does not have the given type defined for the given operator. To resolve it,
  create your own CompilationProtocol.
  

• LimitOperationNotSupportedException

  Summary

  Thrown inside operations related to limits

• MathSException

  Summary

  If one is thrown, the user's input is invalid

• MissingOperatorParseException

  Summary

  Is thrown only when the explicit parsing mode is enabled and the input misses
  some operator, for example, 2x should be 2 * x with explicit parsing mode.
  

• NotSufficientlySupportedException

  Summary

  In case if AM or other parts do not support something,
  for example, it may occur if either AM or SymPy does not
  support some specific feature
  

• NumberCastException

  Summary

  Thrown when invalid cast encountered

• ParseException

  Summary

  Thrown when trying to parse an invalid string

• SolveRequiresStatementException

  Summary

  Thrown if instead of a statement another expression is put into Solve

• TreeException

  Summary

  Thrown when an invalid node or combination of nodes in the expression tree is encountered

• UncompilableNodeException

  Summary

  Thrown when trying to compile and a node cannot be compiled

• UnhandledParseException

  Summary

  Can only occur in the ANTLR parser when it is unclear what exactly happened

• UnrecognizedDomainException

  Summary

  Thrown when non-known domain is passed to the domain function

• WrongNumberOfArgumentsException

  Summary

  Quite general, is thrown when too many or too few of whatever is provided