|
From: | Andrew Janke |
Subject: | [Octave-bug-tracker] [bug #54170] java.lang.String.toCharArray result incorrect conversion to char matrix |
Date: | Sun, 24 Jun 2018 18:23:30 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 |
Follow-up Comment #6, bug #54170 (project octave): I see a few workable alternatives here, in increasing order of difficulty: 1. Convert Java `char` to Octave `uint16` instead of Octave `char` 2. Do not auto-convert Java `char[]`; leave them as Java objects. (This leaves the question of what to do with scalar Java `char`s.) 3. Add a `wchar` type to Octave, and convert Java `char` to that. 4. Change Octave's `char` to be UTF-16, to match Matlab. (See http://lists.gnu.org/archive/html/octave-maintainers/2018-05/msg00137.html) Thoughts on which is preferable in the short term? I may be able to do a patch for 1 or 2. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?54170> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |