Lines Matching refs:API

9 …API is, to a large extent, stable. However, we wish to retain the freedom to make API incompatible…
11 Our goal is that for the 2.1 release (expected in July 2009) most of these parts become API-stable …
13 …API stability is a major concern for our users. That's why it's a priority for us to reach it, but…
17 \li be subject to an API incompatible change;
18 \li introduce API or ABI incompatible changes in your own code if you let them affect your API or A…
22 The following modules are considered entirely experimental, and we make no firm API stability guara…
37 The only classes subject to (even partial) API stability guarantee (meaning that you can safely con…
38 \li MatrixBase : partial API stability (see below)
39 \li Matrix : full API stability (except for experimental stuff inherited from MatrixBase)
40 \li Map : full API stability (except for experimental stuff inherited from MatrixBase)
42 …API guarantee, e.g. their methods can be changed; however notice that most classes inherit MatrixB…
44 A few MatrixBase methods are considered experimental, hence not part of any API stability guarantee: