C programme

[Keith Thompson]

Keith, please feel free to post the missive that you're holding back!

Fine, I'll post it as a followup to your previous article.

 

[Keith Thompson]

Randy Howard wrote: [...]
c.l.c is for discussions of standard C, not platform-specific
discussions.

Isn't comp.std.c *really* the place for *stanard c* questions: I
mean, come on people, this group is *computing DOT languages DOT c*
- i.e., there's nothing in the name that suggests that a newbie
shouldn't ask *anything* that's even *marginally c-related* here
[apart from from the pedantry of some of some of the folks that post
here]

Q. If you were a 'newbie', and had some C related question, where
would you go and ask on the usenet!! ?

<http://groups.google.com/group/comp.lang.c/msg/1460ed5b9ad3dae1?hl=en&>

Sorry - can't [be asked] to follow arbitrary URLs - what's NOT clear about
comp[uting].lang[uages].c?!

Since you can't be bothered to follow a simple URL, here's the
content. It's an article that Jack Klein posted to this newsgroup on
November 20, 2005, in response to a question very similar to yours.
In answer to your question, nothing is unclear about it; you just
don't get it.

] I have no proof, but your question makes me think that you are
] relatively new to usenet.
]
] I've been here for a while, and I've seen good groups destroyed by
] being swamped by off-topic posts.
]
] It was perhaps five or six years ago that comp.lang.c++ was nearly
] destroyed by becoming yet another Visual C++/Windows programming
] group. I know I stopped reading and participating, and quite a few of
] the more knowledgeable regulars disappeared as well. It was only by
] the determined effort of a group of regulars that the group was saved.
]
] Is it really _right_? I think so, and I'll tell you why. Literally
] some of the most knowledgeable experts on C and C++ in the world help
] others on comp.lang.c and comp.lang.c++. That includes, not
] infrequently, members of the language standards committees. There is
] plenty of historical evidence that these are the first to leave when a
] group gets polluted by too much off-topic material.
]
] These groups are far too valuable as resources to be spoiled. For
] every poster who whines that "you can't write a real world program in
] standard C (or C++)", there are many more who realize that you can't
] write any program at all in C or C++ without using standard C or C++,
] and usually far more than you use any extensions or third party
] library.
]
] And as for what the group "should" be about, that's spelled out by the
] name: "comp.lang.c" is nothing but an abbreviation for "computer
] language C". And there is one and only one internationally recognized
] definition of the C programming language, the ANSI/ISO/IEC standard.

Thanks to Netocrat for posting the URL; it confirms something I
mentioned elsewhere in this thread and adds a great deal more detail.

For the record - if one wants to ask *anything* about C, even if it's for
homework, well, I'll at least be not so much *up my own arse* that I'll
simply dismiss it. And **** you as a PS.

For the record, the only reason you're didn't just land in my killfile
is that I don't use one. I'm sure a lot of other readers here are not
so constrained.

We regulars hang out here because we enjoy discussing C and because we
like to help people. We try to maintain the topical focus of this
newsgroup because we believe it is the best way we can do so. You
are, of course, free to disagree with us. We have explained in
considerable detail just why we think this is the best course, and how
alternatives have failed in the past, but if you think the community
would be better served by turning comp.lang.c into
comp.lang.c.whatever, you have every right to hold that opinion. If
you want to whine and pout because somebody corrected an error you
made, or clarified a statement, or whatever it was, you're free to do
that too.

But when you insult and verbally abuse a group of people who are
simply trying to perform a public service, you cross the line.

Until and unless you change your behavior, I will treat you as I treat
any other troll. I'll post corrections if you post any
misinformation, but I will make no effort to be helpful. And I
suspect most other regulars here simply won't see your posts in the
first place.

It's too bad, because I've seen you post sensible articles here in the
past, but that's not enough reason to put up with your whining and
abuse.

Bye.

 

[Emmanuel Delahaye]

Kev P. a écrit :

Hi, I need to do some simple C programming.
I have a really OLD version of Borland Turbo C,
or fairly old Borland C++ v5.0.

However, I expect there is now something free (& better) available
online.

Code::Blocks is the one you want.

http://www.codeblocks.org/

 

[Nick Keighley]

Any comment/code I contribute might =NOT= be 100% portable, nor
semantically correct [read - 'not 100% pedantically correct'].
I don't care too much about that though, and I reckon it's the
same with most 'visitors' here. However, rest assured that any
'essential' (?) corrections WILL almost certainly appear v.soon
[read - 'to add noise as they see fit, a pedant will be along
shortly'].

The fact that factual errors are quickly corrected here is, IMHO, one
of the best features of this newsgroup. I suggest that you *should*
care about correctness, for the sake of the newbies if nothing else.

I find the concept of a programmer who doesn't care about correctness
pretty scary. Let us hope Pemo's programs arn't being used for
anything important.

Given his language and attitude I'm wondering if he's
posting-whilst-drunk

 

[Al Balmer]

Randy Howard wrote: [...]
c.l.c is for discussions of standard C, not platform-specific
discussions.

Isn't comp.std.c *really* the place for *stanard c* questions: I

No. comp.std.c is the place for discussion about the standard itself,
not the language it standardizes.

mean, come on people, this group is *computing DOT languages DOT c*
- i.e., there's nothing in the name that suggests that a newbie
shouldn't ask *anything* that's even *marginally c-related* here
[apart from from the pedantry of some of some of the folks that post
here]

Q. If you were a 'newbie', and had some C related question, where
would you go and ask on the usenet!! ?

<http://groups.google.com/group/comp.lang.c/msg/1460ed5b9ad3dae1?hl=en&>

Sorry - can't [be asked] to follow arbitrary URLs

If you can't be bothered with the answer, why did you ask the
question?

- what's NOT clear about
comp[uting].lang[uages].c?!

What's not clear about "C is the language defined by the C standard."?

For the record - if one wants to ask *anything* about C, even if it's for
homework, well, I'll at least be not so much *up my own arse* that I'll
simply dismiss it. And **** you as a PS.

Then I suggest that you encourage people to email you directly.

===============================================================
In an attempt to reduce 'unwanted noise' on the 'signal' ...

Disclaimer:

Any comment/code I contribute might =NOT= be 100% portable, nor
semantically correct [read - 'not 100% pedantically correct'].

Then I assume you will expect to be corrected.

I don't care too much about that though,

Too bad. Be sure to mention this on your next job interview.

and I reckon it's the
same with most 'visitors' here. However, rest assured that any
'essential' (?) corrections WILL almost certainly appear v.soon
[read - 'to add noise as they see fit, *a pedant* will be along
shortly'].

WARNINGS: Always read the label. No beside-the-point minutiae
filter supplied. Keep away from children. Do not ignite.
===============================================================

 

[Al Balmer]

Secondly, should I really *truly care* if anyone does/doesn't add me to
their 'killfile' [whatever that is: I can guess!] - like, do you or anyone
here think that it's really going to offend -or- upset me in the slightest
if my 'articles' are automagically deleted by some 'clique come quango'
before the members of any subscribing factions 'dain' to read what I might
add, or contribute? Life's too short!

I'm glad you don't mind, and you have more or less correctly guessed
what a killfile is, so enjoy your stay in mine. So far, you have made
no contributions, and it doesn't look likely that you will. Bye, now.

 

[pemo]

[...]
c.l.c is for discussions of standard C, not platform-specific
discussions.

Isn't comp.std.c *really* the place for *stanard c* questions: I

No. comp.std.c is the place for discussion about the standard itself,
not the language it standardizes.

mean, come on people, this group is *computing DOT languages DOT c*
- i.e., there's nothing in the name that suggests that a newbie
shouldn't ask *anything* that's even *marginally c-related* here
[apart from from the pedantry of some of some of the folks that
post here]

Q. If you were a 'newbie', and had some C related question, where
would you go and ask on the usenet!! ?

<http://groups.google.com/group/comp.lang.c/msg/1460ed5b9ad3dae1?hl=en&>

Sorry - can't [be asked] to follow arbitrary URLs

If you can't be bothered with the answer, why did you ask the
question?
!

- what's NOT clear about
comp[uting].lang[uages].c?!

What's not clear about "C is the language defined by the C standard."?

For the record - if one wants to ask *anything* about C, even if
it's for homework, well, I'll at least be not so much *up my own
arse* that I'll simply dismiss it. And **** you as a PS.

Then I suggest that you encourage people to email you directly.

Some kind people here already have - but not with their homework!

===============================================================
In an attempt to reduce 'unwanted noise' on the 'signal' ...

Disclaimer:

Any comment/code I contribute might =NOT= be 100% portable, nor
semantically correct [read - 'not 100% pedantically correct'].

Then I assume you will expect to be corrected.

Certainly I do, esp. if it's a big blunder. But, other than that, no I
don't really. I.e., to save filtering noise form the signal, I'd rather any
'correction' to be of a non-pedantic nature *and* to do with the main thrust
of what's under discussion. If on the other hand it is on some esoteric
issue that's certainly not going to effect me, well, I'll have just have to
read through it, and sigh I guess.

Too bad. Be sure to mention this on your next job interview.

Lucky for me that I don't need one then I've already made my fortune
thanks: and, with only a few grey hairs showing, have since retired to
academia - or whatever it is that might take my fancy - very nice it is too.

But enough of this idle banter, I'm bored with this, as I'm sure everyone
else is.

--
===============================================================
In an attempt to reduce 'unwanted noise' on the 'signal' ...

Disclaimer:

Any comment/code I contribute might =NOT= be 100% portable, nor
semantically correct [read - 'not 100% pedantically correct'].
I don't care too much about that though, and I reckon it's the
same with most 'visitors' here. However, rest assured that any
'essential' (?) corrections WILL almost certainly appear v.soon
[read - 'to add noise as they see fit, *a pedant* will be along
shortly'].

WARNINGS: Always read the label. No beside-the-point minutiae
filter supplied. Keep away from children. Do not ignite.
===============================================================

 

[pemo]

Secondly, should I really *truly care* if anyone does/doesn't add me
to their 'killfile' [whatever that is: I can guess!] - like, do you
or anyone here think that it's really going to offend -or- upset me
in the slightest if my 'articles' are automagically deleted by some
'clique come quango' before the members of any subscribing factions
'dain' to read what I might add, or contribute? Life's too short!

I'm glad you don't mind, and you have more or less correctly guessed
what a killfile is, so enjoy your stay in mine. So far, you have made
no contributions, and it doesn't look likely that you will. Bye, now.

Sob, whimper, tears running down my little face - you've broken my heart.

--
===============================================================
In an attempt to reduce 'unwanted noise' on the 'signal' ...

Disclaimer:

Any comment/code I contribute might =NOT= be 100% portable, nor
semantically correct [read - 'not 100% pedantically correct'].
I don't care too much about that though, and I reckon it's the
same with most 'visitors' here. However, rest assured that any
'essential' (?) corrections WILL almost certainly appear v.soon
[read - 'to add noise as they see fit, *a pedant* will be along
shortly'].

WARNINGS: Always read the label. No beside-the-point minutiae
filter supplied. Keep away from children. Do not ignite.
===============================================================

 

[Mark McIntyre]

Sob, whimper, tears running down my little face - you've broken my heart.

If you plan getting any useful information out of a class, its not
wise persuade the teachers to ignore your questions. The same rule
operates in CLC.

Mark McIntyre

 

[Tydr Schnubbis]

Hi, I need to do some simple C programming.
I have a really OLD version of Borland Turbo C,
or fairly old Borland C++ v5.0.

However, I expect there is now something free (& better) available
online.

Can anyone recommend something.

I'm just a C dabbler, not relly up on C++

TIA, Niv

MS Visual Studio 2005 Express is free. I think you need to also
download the 'Platform SDK' to be able to use the win32 API. It seems
to be a usable IDE, except for the missing profiler.

http://msdn.microsoft.com/vstudio/express/visualC/default.aspx