--- Comment #4 from Vladimir Panteleev <> ---
(In reply to Walter Bright from comment #1)
> Over time, common practice has evolved from rejecting malformed UTF to
> replacing it with replacementDchar, which enables the application (like a
> web browser) to continue processing.

BTW, I don't think this is quite correct. Web browsers both raise an error (in
the dev console) AND continue processing. By using replacementDchar implicitly,
D programs would not know that there was ever a problem.


Reply via email to