«

Chris Dollin wrote:
> lovecreatesbea...@gmail.com wrote:
>
>> This string "0" consists of two characters.
>
> The nul terminator isn't one of the X-Mozilla-Status: 0009ng.

But it IS one of the characters in the char array holding the
string.

--
Chuck F (cbfalconer at maineline dot net)
<http://cbfalconer.home.att.net>
Try the download section.



--
Posted via a free Usenet account from http://www.teranews.com

On Sat, 24 Nov 2007 01:27:26 -0800 (PST), ""
<> wrote:

>what is the difference between a single character and a string
>consisting only one character

Since a string must be terminated with a '\0', the only possible
1-character string is "". If instead you meant a string whose length
is 1, then such a string obviously contains two characters.

A single character can contain any one of at least 256 possible
values.


Remove del for email

CBFalconer wrote:

> Chris Dollin wrote:
>> lovecreatesbea...@gmail.com wrote:
>>
>>> This string "0" consists of two characters.
>>
>> The nul terminator isn't one of the X-Mozilla-Status: 0009ng.

Urm -- what happened there?

> But it IS one of the characters in the char array holding the
> string.

Oh, yes.
Elsethread $)CHarald van D )& k <> (and
what happened /there/? Is my newsgarbler doing something
odd to names & content?) remarks

| From a standards perspective:
| A string is defined as "a contiguous sequence of characters
| terminated by and including the first null character".

which would make my position unsupported by the Standard's
terminology.

--
One-Hand Hedgehog
Notmuchhere: http://www.electrichedgehog.net/

In article <WMa2j.152625$> , Chris
Dollin <> wrote on Sunday 25 Nov 2007 2:26 pm:

> CBFalconer wrote:
>
>> Chris Dollin wrote:
>>> lovecreatesbea...@gmail.com wrote:
>>>
>>>> This string "0" consists of two characters.
>>>
>>> The nul terminator isn't one of the X-Mozilla-Status: 0009ng.
>
> Urm -- what happened there?
>
>> But it IS one of the characters in the char array holding the
>> string.
>
> Oh, yes.
> Elsethread $)CHarald van D )& k <> (and
> what happened /there/? Is my newsgarbler doing something
> odd to names & content?) remarks

No. His name appears mangled on my newsserver/newsreader too. I suspect
that he is using an encoding not supported by some software in the
Usenet hierarchy.

It was fine when Harald started posting to this group, but for a few
months now, his name has not been displayed properly.

> | From a standards perspective:
> | A string is defined as "a contiguous sequence of characters
> | terminated by and including the first null character".
>
> which would make my position unsupported by the Standard's
> terminology.

Yes. So my first post contains errors. Hopefully the OP would have read
far enough into the thread to note the corrections.

In article <fibrpm$mco$>, Harald van D?k
<> wrote on Sunday 25 Nov 2007 6:32 pm:

> On Sun, 25 Nov 2007 12:32:13 +0000, Harald van D?k wrote:
>> On Sun, 25 Nov 2007 14:47:18 +0530, santosh wrote:
>>> It was fine when Harald started posting to this group, but for a few
>>> months now, his name has not been displayed properly.
>>
>> Apparently KNode encoded my name in utf-8, but Pan encodes it in
>> iso-2022-kr. I'll check if there's an option to change that.
>
> Does it display better like this?

Yes. It is now displayed correctly.

Harald van Dijk wrote:
> On Sun, 25 Nov 2007 12:32:13 +0000, Harald van Dijk wrote:
>> On Sun, 25 Nov 2007 14:47:18 +0530, santosh wrote:
>>> It was fine when Harald started posting to this group, but for a few
>>> months now, his name has not been displayed properly.
>> Apparently KNode encoded my name in utf-8, but Pan encodes it in
>> iso-2022-kr. I'll check if there's an option to change that.
>
> Does it display better like this?

Yes.

On Sun, 25 Nov 2007 14:47:18 +0530, santosh wrote:
> In article <WMa2j.152625$> , Chris
> Dollin <> wrote on Sunday 25 Nov 2007 2:26 pm:
>> Oh, yes.
>> Elsethread $)CHarald van D )& k <> (and what
>> happened /there/? Is my newsgarbler doing something odd to names &
>> content?) remarks
>
> No. His name appears mangled on my newsserver/newsreader too. I suspect
> that he is using an encoding not supported by some software in the
> Usenet hierarchy.
>
> It was fine when Harald started posting to this group, but for a few
> months now, his name has not been displayed properly.

Apparently KNode encoded my name in utf-8, but Pan encodes it in iso-2022-
kr. I'll check if there's an option to change that.

Harald van D?k said:

> On Sun, 25 Nov 2007 12:32:13 +0000, Harald van D?k wrote:
>> On Sun, 25 Nov 2007 14:47:18 +0530, santosh wrote:
>>> It was fine when Harald started posting to this group, but for a few
>>> months now, his name has not been displayed properly.
>>
>> Apparently KNode encoded my name in utf-8, but Pan encodes it in
>> iso-2022-kr. I'll check if there's an option to change that.
>
> Does it display better like this?

Yes. But you're still going to have problems with the i-j ligature (or
diphthong, or whatever the proper name is).

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999

On Sun, 25 Nov 2007 12:32:13 +0000, Harald van Dijk wrote:
> On Sun, 25 Nov 2007 14:47:18 +0530, santosh wrote:
>> It was fine when Harald started posting to this group, but for a few
>> months now, his name has not been displayed properly.
>
> Apparently KNode encoded my name in utf-8, but Pan encodes it in
> iso-2022-kr. I'll check if there's an option to change that.

Does it display better like this?

In article <fibo1c$sk3$>, santosh
<> wrote on Sunday 25 Nov 2007 5:28 pm:

> In article <fibrpm$mco$>, Harald van D?k
> <> wrote on Sunday 25 Nov 2007 6:32 pm:
>
>> On Sun, 25 Nov 2007 12:32:13 +0000, Harald van D?k wrote:
>>> On Sun, 25 Nov 2007 14:47:18 +0530, santosh wrote:
>>>> It was fine when Harald started posting to this group, but for a
>>>> few months now, his name has not been displayed properly.
>>>
>>> Apparently KNode encoded my name in utf-8, but Pan encodes it in
>>> iso-2022-kr. I'll check if there's an option to change that.
>>
>> Does it display better like this?
>
> Yes. It is now displayed correctly.

Oops. It was correct when I received and replied to it, but not when I
read it back, as you can see.