Re: [python] StdStringPrinter misleading?

[Phil Muldoon <pmuldoon at redhat dot com>]

Phil Muldoon wrote:
> So I coded in the relevant optional argument logic into the Python 
> sections of the code, and I then passed this length argument to 
> LA_GET_STRING. This does the usual language lookups and (in my example 
> case) resolves to c_get_string. I found to my dismay that with this 
> particular language's get_string implementation I cannot pass a length 
> parameter that it will use. The length parameter passed to it has the 
> length of the string "read" written to it. In c_get_string case the 
> amount read is to the first \0 or if an array, the bounds of that 
> array if that is met first. So we'd have to rewrite c_get_string to 
> pay attention to length if it has a value, and ignore nulls if 
> length_read < length_specified. This makes me a little nervous.
Replying to myself, but Thiago mentioned something on irc that I did not 
read until later. c_get_string uses read_string which does take a length 
argument. The logic just has to be altered to make sure it (the length 
argument) gets there. So that's a happy relief.

I've no idea on the other language string readers. I'll look into them.

Regards

Phil