Hi,
Andy Wingo <wi...@pobox.com> writes:
> On Tue 07 Sep 2010 19:11, l...@gnu.org (Ludovic Courtès) writes:
>
>> Mike Gran <spk...@yahoo.com> writes:
>>
>>> From: Ludovic Courtès <l...@gnu.org>
>>>
>>>> Besides, there’s the undocumented ‘scm_from_stringn’ and the internal
>>>> ‘scm_to_stringn’, which can convert from/to any encoding. I think they
>>>> were initially kept internal because we weren’t quite sure about the
>>>> API. Mike?
>>>
>>> Also, I think we were trying to avoid compilation problems based on
>>> having to expose the libunistring's enum iconv_ilseq_handle to the world.
>>> But later, we ended up creating the analogous
>>> scm_t_string_failed_conversion_handler type to work around that problem.
>>
>> Right. So I guess they can now be made public & documented. Would you
>> like to do it? :-)
>
> Perhaps named scm_{to,from}_encoded_stringn?
FWIW I prefer ‘scm_{to,from}_string’ because (i) with these functions
the encoding as specified as a parameter instead of as part of the
function name (similar to ‘bytevector-u32-native-ref’
vs. ‘bytevector-u32-ref’), and (ii) the word ‘encoded’ doesn’t convey
any piece of information.
Thanks,
Ludo’.
