Update docs for expression parsing improvements
This commit is contained in:
parent
713438e879
commit
8f54f6180a
2 changed files with 13 additions and 7 deletions
|
|
@ -3057,22 +3057,24 @@ is expected in an interface file. For example:
|
|||
<div class="code">
|
||||
<pre>
|
||||
void foo(vector<int> *a, int n);
|
||||
void bar(list<int, 100> *x);
|
||||
void bar(std::array<int, 100> *x);
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
There are some restrictions on the use of non-type arguments. Simple literals
|
||||
are supported, and so are some constant expressions. However, use of '<'
|
||||
and '>' within a constant expressions currently is not supported by SWIG
|
||||
('<=' and '>=' are though). For example:
|
||||
are supported, and so are most constant expressions. However, there are some
|
||||
limitations on the use of '<' and '>' in constant expressions (but note
|
||||
that '<=' and '>=' are fully supported). For example:
|
||||
</p>
|
||||
|
||||
<div class="code">
|
||||
<pre>
|
||||
void bar(list<int, 100> *x); // OK
|
||||
void bar(list<int, 2*50> *x); // OK
|
||||
void bar(list<int, (2>1 ? 100 : 50)> *x) // Not supported
|
||||
void bar(std::array<int, 100> *x); // OK
|
||||
void bar(std::array<int, 2*50> *x); // OK
|
||||
void bar(std::array<int, (1<2 ? 100 : 50)> *x) // OK
|
||||
void bar(std::array<int, 1<2 ? 100 : 50> *x) // Not supported
|
||||
void bar(std::array<int, (2>1 ? 100 : 50)> *x) // Not supported
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue