From c1c706fbd8a2cd0f7dac73a1f5f936dd4eb24826 Mon Sep 17 00:00:00 2001
From: Simon Marchetto <simon.marchetto@scilab-enterprises.com>
Date: Mon, 16 Jun 2014 17:08:25 +0200
Subject: [PATCH] scilab: update doc (unsigned ints typemaps changes)

---
 Doc/Manual/Scilab.html | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/Doc/Manual/Scilab.html b/Doc/Manual/Scilab.html
index a1ba7f8e2..dfcf3959c 100644
--- a/Doc/Manual/Scilab.html
+++ b/Doc/Manual/Scilab.html
@@ -1351,13 +1351,13 @@ The following table provides the equivalent Scilab type for C/C++ primitive type
 <tr><td>bool</td><td>boolean</td></tr>
 <tr><td>char</td><td>string</td></tr>
 <tr><td>signed char</td><td>double or int8</td></tr>
-<tr><td>unsigned char</td><td>uint8</td></tr>
+<tr><td>unsigned char</td><td>double or uint8</td></tr>
 <tr><td>short</td><td>double or int16</td></tr>
-<tr><td>unsigned short</td><td>uint16</td></tr>
+<tr><td>unsigned short</td><td>double or uint16</td></tr>
 <tr><td>int</td><td>double or int32</td></tr>
-<tr><td>unsigned int</td><td>uint32</td></tr>
+<tr><td>unsigned int</td><td>double or uint32</td></tr>
 <tr><td>long</td><td>double or int32</td></tr>
-<tr><td>unsigned long</td><td>uint32</td></tr>
+<tr><td>unsigned long</td><td>double or uint32</td></tr>
 <tr><td>signed long long</td><td>not supported in Scilab 5.x</td></tr>
 <tr><td>unsigned long long</td><td>not supported in Scilab 5.x</td></tr>
 <tr><td>float</td><td>double</td></tr>
@@ -1370,15 +1370,14 @@ The following table provides the equivalent Scilab type for C/C++ primitive type
 Notes:
 <ul>
 <li>In Scilab the <tt>double</tt> type is used far more than any integer type.
-This is why signed integer values (<tt>short, int, integer, long</tt>) are automatically converted to Scilab <tt>double</tt> values when marshalled from C into Scilab.
-Additionally on input to a C function, Scilab <tt>double</tt> values are converted from into the related integer type.
-Unsigned integers are not concerned by these conversions.
+This is why integer values (<tt>int32</tt>, <tt>uint32</tt>, ...) are automatically converted to Scilab <tt>double</tt> values when marshalled from C into Scilab.
+Additionally on input to a C function, Scilab <tt>double</tt> values are converted into the related integer type.
 </li>
 <li>
 When an integer is expected, if the input is a double, the value must be an integer, i.e. it must not have any decimal part, otherwise a SWIG value error occurs.
 </li>
 <li>
-In SWIG for Scilab 5.x the <tt>long long</tt> type is not supported since Scilab 5.x does not have a 64-bit integer type.
+In SWIG for Scilab 5.x, the <tt>long long</tt> type is not supported, since Scilab 5.x does not have a 64-bit integer type.
 The default behaviour is for SWIG to generate code that will give a runtime error if <tt>long long</tt> type arguments are used from Scilab.
 </li>
 </ul>