On Wed, 25 Oct 2000, Mark Leisher wrote: > There may some day be a use for the Unicode codepoint 0x0000. It might be > better to make this 0xFFFF, which is a guaranteed non-character in Unicode and > probably in ISO10646. Isn't that the natural character to use for null-terminated strings? For example, if I'm processing UTF-8 text in C, "foo" is equivalent to 0066 006F 006F 0000. In which case, it's very much in use already. Cheers, Philip -- Philip Newton <[EMAIL PROTECTED]>
- Re: Encode's .enc files and a question Nick Ing-Simmons
- Re: Encode's .enc files and a question Mark Leisher
- Re: Encode's .enc files and a question Nick Ing-Simmons
- Re: Encode's .enc files and a question Mark Leisher
- Re: Encode's .enc files and a question Philip Newton
- Re: Encode's .enc files and a question Nick Ing-Simmons
- Re: Encode's .enc files and a question Mark Leisher
- Re: Encode's .enc files and a question Nick Ing-Simmons
- Re: Encode's .enc files and a question Peter Prymmer
- Re: Encode's .enc files and a question Nick Ing-Simmons
- Re: Encode's .enc files and a question Philip Newton
- Re: Encode's .enc files and a question Mark Leisher
- Re: Encode's .enc files and a question Peter Prymmer
- Re: Encode's .enc files and a question Philip Newton
- Re: Encode's .enc files and a question Mark Leisher
- Re: Encode's .enc files and a question Nick Ing-Simmons