Hi all,

The first release candidate for the CellML API 1.11 (1.11-rc1) has been released. This release candidate will become the CellML API 1.10 if no-one reports any problems with it by next Wednesday (New Zealand time). Please try out the the API and report any problems on the Physiome Tracker at https://tracker.physiomeproject.org/, by e-mailing cellml-tools-develop...@cellml.org (you will need to subscribe to the list first using this page: http://lists.cellml.org/mailman/listinfo/cellml-tools-developers), or by e-mailing ak.mil...@auckland.ac.nz.

The files making up this release candidate are available here:
  * http://www.cellml.org/tools/downloads/cellml_api/releases/1.11rc1

New features and bugfixes:
* The CellML Generics and Reflection Service lets you write code that can access the list of available API services, operations, and attributes. This can be used to write generic code that works over the entire API without needing to hard-code the details of the part of the API being called. This has application for creating certain types of user interfaces, as well as for creating language bindings. * The Python bindings have been re-written and are now shipped as a Python egg, separately from the CellML API itself. The new Python bindings use the Generics & Reflection service to provide a more idiomatic and more convenient interface to the CellML API from Python. * A number of bugfixes have been made, including bugfixes to the code generation which could have resulted in bad numerical results. * The C++ interface has been revised to be more idiomatic - strings are now returned using the STL std::string and std::wstring types, and sequences are returned as std::vector types. Objects are returned using the already_AddRefd wrapper so users no longer need to use the RETURN_INTO_OBJREF macro to manage reference counts easily, instead they can simply assign into an ObjRef. The RETURN_INTO_OBJREF macros remain available for legacy code.

Best wishes,

cellml-discussion mailing list

Reply via email to