Skip to content

Releases: codingseb/ExpressionEvaluator

1.4.21.0

27 Feb 19:03
08ce89c

Choose a tag to compare

  • Correction of a bug introduced in previous version (Manage implicit cast of method args again) (See #87 Thanks to @leniency)

1.4.20.0

24 Feb 19:23
061bb55

Choose a tag to compare

  • Add support for ref, out and in keyword in methods calls
  • Add support for calling method with params keyword array parameters

Thanks to @olegbevz for issue #83 and to @lofcz for suggestions

1.4.19.0

03 Feb 10:27
5d3d1f5

Choose a tag to compare

  • Correction of the bug : #81 Exceptions are assigned to variables (Thank to @haering)
  • List of corresponding extensions methods in exception when wrong override is used (See #75 Thanks to @lofcz)
  • Text correction in exception

1.4.18.0

04 Jan 15:23
c90aaab

Choose a tag to compare

  • Better exception when expression is empty (Thanks to @lofcz See #70)

1.4.17.0

11 Dec 08:39
a35580f

Choose a tag to compare

1.4.16.0

23 Sep 06:21
bfc3e6a

Choose a tag to compare

  • Bug Correction : When a ExpandoObject had a Property set to null an exception was thown that no property was found (Thanks to @doug-episource see #67)

1.4.15.0

02 Sep 07:08
86fb575

Choose a tag to compare

  • Add a Hack to better manage overloaded Linq methods define in Enumerable (Sum, Average, Min and Max...) (See #65 Thanks to @TheoVC)

1.4.14.0

14 Aug 07:50
e041541

Choose a tag to compare

  • Support for Unicode naming (variables, types, methods...) to support coding in languages like (Chinese, Korean, Japenese...) (Thanks to @minogram see #63)

1.4.13.0

15 Jul 13:20
e2601a0

Choose a tag to compare

  • More complete Corrections of the bug on && and || operators when the right part throw an exception when only the left part should be evaluated (#56 again)
  • Correction of a bug when creating an exception without throwing (introduced in last release)
  • Some refactoring

1.4.12.0

11 Jul 15:27
b9bc766

Choose a tag to compare

  • Correction of a bug on && and || operators when the right part throw an exception when only the left part should be evaluated (See #56 A great thank to @HelgeL and @Karbot to reporting this bug and for their wonderful solution)