HOWTO: const and pointer variants in C and C++ : c++

James Kuyper wrote, On 11/11/08 19:12:
> pete wrote:

<snip>

>> In order to make a point,
>> you would have to post a correct c program
>
> In case you haven't noticed, this message is cross-posted to two groups
> where C++ code is entirely appropriate; the Subject: line might also be
> a hint.

It is also posted to a group where C++ is NOT topical. The way pete
indicated this might not be the best, but it is certainly true that the
example given was not correct for comp.lang.c where only C is topical.
Is it really too difficult for people with C++ specific answers to drop
the cross-post to comp.lang.c?
--
Flash Gordon
If spamming me sent it to smap@spam.causeway.com
If emailing me use my reply-to address
See the comp.lang.c Wiki hosted by me at http://clc-wiki.net/

Flash Gordon wrote:
>
> Is it really too difficult for people with C++ specific answers to drop
> the cross-post to comp.lang.c?

Dropping is not difficult. _Noticing_ might be. I, for one, use
Thunderbird and most of the time don't notice that I post to multiple
newsgroups at once.

--
Best regards,
Andrey Tarasevich

Flash Gordon wrote:
>
> Is it really too difficult for people with C++ specific answers to drop
> the cross-post to comp.lang.c?

Dropping is not difficult. _Noticing_ might be. I, for one, use
Thunderbird and most of the time don't notice that I post to multiple
newsgroups at once.

--
Best regards,
Andrey Tarasevich

On 2008-11-11 15:16:00 -0500, Flash Gordon <smap@spam.causeway.com> said:

> James Kuyper wrote, On 11/11/08 19:12:
>> pete wrote:
>
> <snip>
>
>>> In order to make a point,
>>> you would have to post a correct c program
>>
>> In case you haven't noticed, this message is cross-posted to two groups
>> where C++ code is entirely appropriate; the Subject: line might also be
>> a hint.
>
> It is also posted to a group where C++ is NOT topical. The way pete
> indicated this might not be the best, but it is certainly true that the
> example given was not correct for comp.lang.c where only C is topical.
> Is it really too difficult for people with C++ specific answers to drop
> the cross-post to comp.lang.c?

It's no more difficult than for people with comments about the
appropriateness of postings in comp.lang.c to drop the cross-post to
comp.lang.c++.

--
Pete
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The
Standard C++ Library Extensions: a Tutorial and Reference
(www.petebecker.com/tr1book)

On 2008-11-11 15:16:00 -0500, Flash Gordon <smap@spam.causeway.com> said:

> James Kuyper wrote, On 11/11/08 19:12:
>> pete wrote:
>
> <snip>
>
>>> In order to make a point,
>>> you would have to post a correct c program
>>
>> In case you haven't noticed, this message is cross-posted to two groups
>> where C++ code is entirely appropriate; the Subject: line might also be
>> a hint.
>
> It is also posted to a group where C++ is NOT topical. The way pete
> indicated this might not be the best, but it is certainly true that the
> example given was not correct for comp.lang.c where only C is topical.
> Is it really too difficult for people with C++ specific answers to drop
> the cross-post to comp.lang.c?

It's no more difficult than for people with comments about the
appropriateness of postings in comp.lang.c to drop the cross-post to
comp.lang.c++.

--
Pete
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The
Standard C++ Library Extensions: a Tutorial and Reference
(www.petebecker.com/tr1book)

Pete Becker wrote, On 11/11/08 20:24:
> On 2008-11-11 15:16:00 -0500, Flash Gordon <smap@spam.causeway.com> said:
>
>> James Kuyper wrote, On 11/11/08 19:12:
>>> pete wrote:
>>
>> <snip>
>>
>>>> In order to make a point,
>>>> you would have to post a correct c program
>>>
>>> In case you haven't noticed, this message is cross-posted to two groups
>>> where C++ code is entirely appropriate; the Subject: line might also be
>>> a hint.
>>
>> It is also posted to a group where C++ is NOT topical. The way pete
>> indicated this might not be the best, but it is certainly true that the
>> example given was not correct for comp.lang.c where only C is topical.
>> Is it really too difficult for people with C++ specific answers to drop
>> the cross-post to comp.lang.c?
>
> It's no more difficult than for people with comments about the
> appropriateness of postings in comp.lang.c to drop the cross-post to
> comp.lang.c++.

I had not registered that it was James Kuyper, who does read
comp.lang.c, who made the comment above about it being topical in two of
the groups this is cross-posted to. Sorry. If I had registered I would
have dropped the cross-post.

In general where threads are cross-posted between comp.lang.c and
comp.lang.c++ it is people who don't read comp.lang.c who post messages
cross-posted to it which are not topical "here", so in general making
such a comment just in comp.lang.c can't do any good. People in all
three of these groups (including comp.lang.c) need to watch out for
cross-posts and drop comp.ang.c++ where it is a C specific answer, and
comp.lang.c where it is a C++ answer, and tell the OP what a bad idea
the cross-post is because of the problems it causes.
--
Flash Gordon
If spamming me sent it to smap@spam.causeway.com
If emailing me use my reply-to address
See the comp.lang.c Wiki hosted by me at http://clc-wiki.net/

Pete Becker wrote, On 11/11/08 20:24:
> On 2008-11-11 15:16:00 -0500, Flash Gordon <smap@spam.causeway.com> said:
>
>> James Kuyper wrote, On 11/11/08 19:12:
>>> pete wrote:
>>
>> <snip>
>>
>>>> In order to make a point,
>>>> you would have to post a correct c program
>>>
>>> In case you haven't noticed, this message is cross-posted to two groups
>>> where C++ code is entirely appropriate; the Subject: line might also be
>>> a hint.
>>
>> It is also posted to a group where C++ is NOT topical. The way pete
>> indicated this might not be the best, but it is certainly true that the
>> example given was not correct for comp.lang.c where only C is topical.
>> Is it really too difficult for people with C++ specific answers to drop
>> the cross-post to comp.lang.c?
>
> It's no more difficult than for people with comments about the
> appropriateness of postings in comp.lang.c to drop the cross-post to
> comp.lang.c++.

I had not registered that it was James Kuyper, who does read
comp.lang.c, who made the comment above about it being topical in two of
the groups this is cross-posted to. Sorry. If I had registered I would
have dropped the cross-post.

In general where threads are cross-posted between comp.lang.c and
comp.lang.c++ it is people who don't read comp.lang.c who post messages
cross-posted to it which are not topical "here", so in general making
such a comment just in comp.lang.c can't do any good. People in all
three of these groups (including comp.lang.c) need to watch out for
cross-posts and drop comp.ang.c++ where it is a C specific answer, and
comp.lang.c where it is a C++ answer, and tell the OP what a bad idea
the cross-post is because of the problems it causes.
--
Flash Gordon
If spamming me sent it to smap@spam.causeway.com
If emailing me use my reply-to address
See the comp.lang.c Wiki hosted by me at http://clc-wiki.net/

On 11 Nov 2008 at 21:20, Flash Gordon wrote:
> People in all three of these groups (including comp.lang.c) need to
> watch out for cross-posts and drop comp.ang.c++ where it is a C
> specific answer, and comp.lang.c where it is a C++ answer,

You might /like/ people to do this for your own political reasons. But
they don't /need/ to. They can do whatever they think is appropriate,
whether it suits your prejudices or not.

> and tell the OP what a bad idea the cross-post is because of the
> problems it causes.

There is no problem - you just choose to believe there is for your own
political reasons.

On 11 Nov 2008 at 21:20, Flash Gordon wrote:
> People in all three of these groups (including comp.lang.c) need to
> watch out for cross-posts and drop comp.ang.c++ where it is a C
> specific answer, and comp.lang.c where it is a C++ answer,

You might /like/ people to do this for your own political reasons. But
they don't /need/ to. They can do whatever they think is appropriate,
whether it suits your prejudices or not.

> and tell the OP what a bad idea the cross-post is because of the
> problems it causes.

There is no problem - you just choose to believe there is for your own
political reasons.

James Kuyper wrote:
> pete wrote:
>> Hendrik Schober wrote:
>>> pete wrote:
>>>> [...]
>>>> I don't think that removing const
>>>> ever changes the semantics of a program.
>>>
>>> struct test {
>>> int f() {return 1;}
>>> int f() const {return 0;}
>>> };
>>>
>>> int main()
>>> {
>>> /*const*/ test x;
>>> return x.f();
>>> }
>>
>> In order to make a point,
>> you would have to post a correct c program
>
> In case you haven't noticed, this message is cross-posted to two groups
> where C++ code is entirely appropriate;

I hadn't noticed.

> the Subject: line might also be a hint.

--
pete