ILCalc v0.9.2.1

Rating: No reviews yet
Downloads: 171
Released: Apr 18, 2009
Updated: May 4, 2009 by Pelmen64
Dev status: Stable Help Icon

Recommended Download

Application Source Code
application, 257K, uploaded Apr 18, 2009 - 40 downloads

Other Available Downloads

Example Demo Application
example, 111K, uploaded Apr 18, 2009 - 33 downloads
Application Library (.NET 2.0)
application, 90K, uploaded Apr 18, 2009 - 24 downloads
Application Library (.NET CF 3.5)
application, 80K, uploaded Apr 20, 2009 - 21 downloads
Application Library (Silverlight 2.0)
application, 79K, uploaded Apr 18, 2009 - 19 downloads
Documentation Documentation
documentation, 392K, uploaded Apr 18, 2009 - 34 downloads

Release Notes

New stable release with a pack of small improvements.

Changes:
  • Solution: this changelog included.
  • Solution: directory structure redone.
  • FunctionCollection: completely rewritten.
  • FunctionCollection: added small support for delegates.
  • Engine: some improvements in method calls.
  • Rename: FunctionCollection => FunctionDictionary.
  • Rename: ConstantCollection => ConstantDictionary.
  • Documentation: many fixes, added new Functions API.
  • Interpret: all known bugs are fixed, serialization works now.
  • Interpret: performance increase (replacing collections with arrays).
  • Interpret: fully immutable now (but not thread-safe!).
  • Interpret: added EvaluateSync() - thread-safe version of Evaluate().
  • TabRange: serializable (just forget to mark it with attribute).
  • TabRange: explictly implements IEnumerable<double>.
  • TabRange: Count property value calculation is cached now.
  • IEvaluator: was removed from SL/CF versions (no need for it).
  • Unit Tests: improved + new (for thread-safety).

Known bugs:
  • Function folding optimization works wrongly with methods, containing parameters arrays.
  • Troubles with MissingManifestResourceException on CF3.5 version. Library re-uploaded, but source code still old (you may simply place Resources.resx to the root of the project and clear the Custom Tool Namespace field in the resources properties).

Reviews for this release

No reviews yet for this release.