Kenichi Handa [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED], Jan D. [EMAIL PROTECTED] writes:
If the multibyte string is generated by an error and this is one of the
places where we can detect the error, should we not keep the xassert?
[EMAIL PROTECTED] (Kim F. Storm) writes:
I
I agree that signaling an error is better than xassert.
But, it seems that a function in selection-converter-alist
can return a multibyte string as long as we have a fixed
rule about how to handle it. And converting to a unibyte
string by string-make-unibyte seems to be a good rule.
Normally, the caller would instead use `STRING_SET_UNIBYTE' after the
call
(or rather calls one of make_foo_string which does it for him) if
needed.
This is not the same as what I suggested, but this too is ok.
However, if we stick with this, we should document it better
in
In article [EMAIL PROTECTED], Jan D. [EMAIL PROTECTED] writes:
If the multibyte string is generated by an error and this is one of the
places where we can detect the error, should we not keep the xassert?
[EMAIL PROTECTED] (Kim F. Storm) writes:
I agree, but since the source of the error is
