Backward compatibility -> Compatibility Note
This commit is contained in:
parent
6b18d20979
commit
e48c2ce35e
1 changed files with 2 additions and 2 deletions
|
|
@ -1378,7 +1378,7 @@ Now, from Lua usage is as follows:
|
||||||
0
|
0
|
||||||
>
|
>
|
||||||
</pre></div>
|
</pre></div>
|
||||||
<H4> Backward compatibility </H4>
|
<H4> Compatibility Note </H4>
|
||||||
<p>
|
<p>
|
||||||
If SWIG is running in backward compatible way, i.e. without <tt>-no-old-metatable-bindings</tt> option, then additional old-style names are generated(notice the underscore):
|
If SWIG is running in backward compatible way, i.e. without <tt>-no-old-metatable-bindings</tt> option, then additional old-style names are generated(notice the underscore):
|
||||||
</p>
|
</p>
|
||||||
|
|
@ -1390,7 +1390,7 @@ If SWIG is running in backward compatible way, i.e. without <tt>-no-old-metatabl
|
||||||
11
|
11
|
||||||
>
|
>
|
||||||
</pre></div>
|
</pre></div>
|
||||||
<H3> Backward compatibility </H3>
|
<H3> Compatibility Note </H3>
|
||||||
<H4> Names </H4>
|
<H4> Names </H4>
|
||||||
<p> If SWIG is launched without <tt>-no-old-metatable-bindings</tt> option, then it enters backward-compatible mode. While in this mode, it tries
|
<p> If SWIG is launched without <tt>-no-old-metatable-bindings</tt> option, then it enters backward-compatible mode. While in this mode, it tries
|
||||||
to generate additional names for static functions, class static constants and class enums.
|
to generate additional names for static functions, class static constants and class enums.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue