passing a union's field to a function

[Racaille]

Ugh, that's worse. In my newsreader, it shows up with a bunch of
non-printable '\232' characters.

That is 'no-break space' (&nbsp in the koi8-r charset.
That is probably what you get for spaces when you try to copy'n'paste
from
one of those fancy newsreaders

 

[Al Balmer]

Actually, they don't -- many use proportional fonts, which is rather a
nuissance, when it comes to software code.

I've never seen a newsreader that couldn't be told to use a fixed
font. Care to name a couple of the many? I have seen newsreaders that
didn't provide proportional fonts (but not for a long time.)

 

[Michael Mair]

Mikhail Teterin said:

Did my second response not count as actual advice on the subject matter?
Hmm.

Well, at least the OP responded to yours... ;-)

Cheers
Michael

 

[Dik T. Winter]

>
> I just saved it back to a file from the news-reader. The file is perfectly
> clean, opens up fine in vi, and compiles...

The code \232 is apparently an additional space in the Koi-8 codes
that also implement line drawing symbols. A Cyrillic space? Not
everybody is equiped with newsreaders that understand those Koi-8
codes, and for most of them is \232 is a code that they do not
understand (it is a control code in all versions of ISO 8859, and
in standard Koi-8).

 

[Dik T. Winter]

> Robert Gamble wrote:
>
>
> The reason being?..

That not everybody has the same tab settings as you.

 

[Dik T. Winter]

> Mikhail Teterin schrieb: ....
>
> There are no clear, standardized rules.
> Example:
> What happens for
> union foo {
> float bar;
> long double baz;
> void *qux;
> int *quux;
> };
> if you perform
> union foo Foo = 0;
> As a cast is only an explicit conversion, this is the same
> as
> union foo Foo = (union foo) 0;
>
> Do we get the representation of 0.0F, 0.0L, (void *)0, or (int *)0?
> Note: the latter two may in theory differ.

In theory all four may differ, but I have never encountered a system
where that was the case. But I have encountered systems where the
first three were different, while the size of the first and the
third was the same. Different systems. On one, 0.0F was not all bits
0, on the other (void *)0 was not all bits 0.

 

[Dik T. Winter]

>
> Come on -- that's not a valid argument. The attachements have appeared more
> than 10 years ago and all news-readers (including text based ones) now
> support them.

Well, the news-reader I am using would not recognise an attachment when you
waved it in front of its eyes. Consider, it is just piping the article
contents through "more". (Not really, but it is very similar.)

 

[Dik T. Winter]

....
> Incidentally, your followup added a '\232' character before the word
> "They" in the text that you quoted (I've kept it in this followup).
> You might want to find out why your newsreader, or maybe your server,
> is doing this, and persuade it to stop.

Nope, he is just using a space that is present in the Koi-8 encoding,
instead of the standard space.

 

[Dik T. Winter]

> On Fri, 11 Aug 2006 18:44:47 -0400, Mikhail Teterin

> I've never seen a newsreader that couldn't be told to use a fixed
> font. Care to name a couple of the many? I have seen newsreaders that
> didn't provide proportional fonts (but not for a long time.)

My newsreader is using the font that the window is using where it displays
the articles. In this case just the window of a telnet session, but I
could have told the telnet session to use a proportional font.

 

[Michael Mair]

In theory all four may differ,

Argh -- of course I meant that the first three are more likely to
differ... *sigh*
Thank you for making that clearer.

but I have never encountered a system
where that was the case. But I have encountered systems where the
first three were different, while the size of the first and the
third was the same. Different systems. On one, 0.0F was not all bits
0, on the other (void *)0 was not all bits 0.

The former, 0.0F not being all bits zero, I have also encountered.


Cheers
Michael

 

[Mikhail Teterin]

Well, the news-reader I am using would not recognise an attachment when
you waved it in front of its eyes. šConsider, it is just piping the
article contents through "more". š(Not really, but it is very similar.)

The textual, unencoded attachment should be just as visible through more, as
the text beyond the customary "------ cut here ------" is...

Is it not?

-mi