mprintf, msprintf, mfprintf: the "%c" format is badly handled: providing US-ASCII codes yields errors

Reported by Samuel GOUGEON (@sgougeon)

BUG DESCRIPTION:
----------------
mprintf("%c\n", 65), msprintf("%c\n", 65), mfprintf(fid, "%c\n", 65) should print ascii(65)=="A".

Instead, an error is yielded:
--> mprintf("%c\n", 65)

mprintf: Wrong number of input arguments: data doesn't fit with format.

--> msprintf("%c\n", 65)

msprintf: Wrong number of input arguments: data doesn't fit with format.


ERROR LOG:
----------


HOW TO REPRODUCE THE BUG:
-------------------------
mprintf("%c\n", 65)
msprintf("%c\n", 65)


OTHER INFORMATION:
------------------
Instead of a US-ASCII code expected as documented (), Scilab actually accept strings.
Up to Scilab 5.5, only the first character of the input string was printed.
-->msprintf("AB %c\n", "123")
 ans  =
 AB 1   

Since Scilab 6.0.0, the full input string is printed:
--> msprintf("AB %c\n", "123")
 ans  =
  "AB 123"

It looks like Scilab has always been wrong for handling "%c":

added 6.1.0 Bugzilla Input / output Minor labels

By Samuel GOUGEON (@sgougeon)

Instead of a US-ASCII code expected as documented () https://help.scilab.org/docs/6.1.0/en_US/printf_conversion.html

See also http://mailinglists.scilab.org/Scilab-users-mprintf-quot-c-quot-actual-action-and-vs-mprintf-quot-s-quot-tt4041072.html

marked this issue as related to #13303 (closed)

mentioned in issue #13303 (closed)