This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v1 02/36] Guile extension language: doc additions

Doug Evans <> skribis:

> On Sat, Jan 4, 2014 at 3:57 AM, Ludovic CourtÃs <> wrote:
>>>> >> +A Scheme string is converted to a target string, using the current
>>>> >> +target encoding.
>>>> >
>>>> > What if target encoding doesn't support some of the characters in the
>>>> > string?
>>>> Guileâs behavior can be controlled with
>>>> â%default-port-conversion-strategyâ: it can raise an exception, or
>>>> substitute any characters that could not be converted, or escape them
>>>> (info "(guile) Ports").
>>>> Perhaps this should be briefly mentioned, with a cross-ref.
>>> It should, because the issue will certainly arise, especially since
>>> (AFAIU) Guile prefers UTF-8.
>> Right.  (UTF-8 is just the default encoding for source code; itâs not
>> âpreferredâ in any other way.)
> The default conversion strategy here (for make-value) is to throw an exception.
> This isn't a port, and it doesn't feel right to use
> %default-port-conversion-strategy here.

Yes, but I mentioned it because scm_{fo,from}_locale_string use the
value of that fluid as their conversion strategy (info "(guile)
Conversion to/from C").

> It's easy enough to add #:encoding and #:errors options to make-value
> in a later patch.

Yes, that would be best.

(Actually, instead of keyword parameters, you could use optional
positional parameters like âstring->bytevectorâ.)

>>>> >> +If the optional @var{length} argument is given, the string will be
>>>> >> +fetched and encoded to the length of characters specified.  If
>>>> >> +the @var{length} argument is not provided, the string will be fetched
>>>> >> +and encoded until a null of appropriate width is found.
>>>> >
>>>> > Isn't this null termination description skewed towards C-like
>>>> > languages?  Aren't there languages where strings don't have to be
>>>> > null-terminated?
>>>> Yes, and thatâs when LENGTH should be provided, AIUI.
>>> Then I guess the above should say that explicitly.  But it would be
>>> nice if GDB could support strings in languages that don't
>>> null-terminate even without LENGTH.
>> Agreed (I had misread the description above as saying that, if LENGTH is
>> provided, then the string is *not* assumed to be nul-terminated.)
> I think the text that is there now is sufficient, I'm not sure how I
> would change it.
> I'm happy to apply any suggested rewordings.
> Note that as far as functionality goes, what's there now is what gdb provides.
> ref: LA_GET_STRING, struct language_defn.la_get_string.
> Any additional functionality can be added later.

If the functionality is that only null-terminated strings are supported,
then the text is fine.

Eli was suggesting supporting non-null-terminated strings as well, but
indeed, that can always be added later.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]