Search results
Feb 22, 2024 · On 20.02.2024 19:26, Lew Pitcher wrote: > On Tue, 20 Feb 2024 18:10:30 +0000, Richard Harnden
This page is the top of an HTML version of the Usenet comp.lang.c Frequently Asked Questions list (also known as the "clc FAQ").
- 1 Introduction and Topicality
- 2 Posting to comp.lang.c
- 3 Reading comp.lang.c
- 4 Resources
- 5 Off-Topic Pointers, Pedantry and Friendliness
- Shortcut Links For Usenet Posting
It's a good idea to read at least the posting and topicality guidelines through before posting to comp.lang.c - lack of understanding carries risk of public embarrassment or confrontation. The group's FAQis a separate, technical document.
2.1 What should I do before posting a question?
Lurk for at least a couple of weeks or review at least a couple of weeks worth of posts to get an understanding of the group's posting norms and to check that your question has not recently been asked and answered. Read How To Ask Questions The Smart Wayby Eric Steven Raymond and Rick Moen. Then as a rough checklist, verify that: 1. your question is topical (see the previous section) 2. your question is not answered in the FAQ or a basic C textbook, and if it's homework, that you're following...
2.2 How should I ask homework questions?
Most posters to comp.lang.c will not provide ready-made solutions to obvious homework questions, but are generally willing to provide advice and guidance if you have at least attempted to answer the question yourself. Here's an annotated reference post: 1. Clearly state that your question is homework.Pretending that it's not doesn't work in comp.lang.c. You are also likely to get answers that, if you use them, will make it obvious that you did not do the work yourself. 2. Clearly state the pr...
2.3 What should I avoid when posting?
1. Excessive capitalisation (the internet equivalent of shouting) or lack of capitalisation where it's usual, such as at the beginning of sentences. 2. Abbreviations like "u" for "you" or "pls" for "please", because it can be harder for readers not accustomed to them to parse them, especially for non-native speakers, and because most regulars of comp.lang.c by virtue of their appreciation for correct C (a programming language) also appreciate correct English (a human language). 3. Asking for...
3.1 What are good reasons to read comp.lang.c?
1. to learn how to write portable C code - portable in the sense that it's guaranteed to run correctly on any Standard-conforming implementation 2. to learn what is and what isn't portable C, and why 3. to pick up portable C tricks and tips 4. to learn and practice effective reasoning, written communication and debating skills.
3.2 What do the commonly used acronyms mean?
1. OP stands for "Original Poster" 2. OT stands for "Off-Topic". 3. UB stands for "Undefined behaviour". 4. C&V stands for "Chapter and Verse" and indicates that the writer wants a direct pointer to the relevant section of the Standard. The meanings of various other acronyms can be discovered through The Jargon File, Urban Dictionary, a general web search or by installing the wtf program.
4.1 What does the FAQ cover?
The C FAQis maintained by Steve Summit and is commonly referred to by regulars. The FAQ contains diverse material, from arrays and pointers to the preprocessor to style, and is suitable for programmers of all levels of ability. It's technical and can be read in isolation from the comp.lang.c newsgroup, so posting conventions aren't described there, but checking for an answer in the FAQ prior to posting a question is essential - it's a waste of time and bandwidth to post something addressed by...
4.2 Where can I find out about or obtain the Standard?
Refer to The C Standard#Obtaining_the_Standard. Access to at least a draft version of the Standard is useful for those intending to participate significantly in comp.lang.c.
4.3 Where can I get a compiler or IDE?
Refer to C resources:IDEs and C resources:Compilers.
5.1 Why do so many responses point out that a post is off-topic?
Many (new or posing-as-new) posters don't follow the norms of the group. The reason is probably one or more of: 1. ignorance that norms exist 2. a deliberate attempt to annoy some readers or posters 3. a deliberate (implicit or explicit) assertion that the norms are illegitimate or should be changed. It's certain that at least some of the posts are deliberate attempts to annoy (trollposts). It's also certain that many newcomers (particularly from Google groups) often simply aren't aware of th...
5.2 What's the role and effect of pedantry in comp.lang.c?
As a focussed technical newsgroup, comp.lang.c partly depends on an approach near enough to pedantic that the group's etiquette allows for pedantry. C is governed by an international Standard that leaves much undefined and that requires careful interpretation. Without pedantic responses many subtle errors and intricacies would not be pointed out to readers. "Pedantic" is probably also one part of the description of the thought processes required for or acquired whilst programming and debuggin...
5.3 Is comp.lang.c a friendly group?
Some argue that pedantry and repetitive instruction of group norms combine to encourage a surly, unfriendly and overly combative environment where many posters' real questions, by being deemed off-topic, aren't answered and the emphasis is on being right at all costs. There have been campaigns for a friendlier comp.lang.c in the past. The genuine expertise that resides in the group is probably one mitigating factor for those who consider aspects of comp.lang.c unfriendly yet who continue to f...
The page Introduction to comp.lang.c redirects here, so a convenient short url for posting to Usenet is: http://clc-wiki.net/wiki/intro_to_clc(the "i" in intro can optionally be capitalised). Also, the number preceding each question hyperlinks to a briefer direct url than provided by MediaWiki by default when clicking on the question in the table o...
Covers C in 5 levels (encounter, acquaintance, cognition, experience, ambition) from beginning C to advanced C. It covers C11 and C17, including threads and atomic access, which few other books do. Not all compilers recognize these features in all environments.
Jun 27, 2024 · Welcome to clc-wiki, an offshoot of the comp.lang.c newsgroup. Good places to start are the introduction to comp.lang.c and the about page for this wiki.
This page is the top of an HTML version of the Usenet comp.lang.c Frequently Asked Questions (FAQ) list.
People also ask
What is Comp Lang c & how is it accessed?
Is Comp Lang a good place to learn C?
How important is accuracy in Comp Lang?
What is the C FAQ?
May 30, 2018 · 50 votes, 13 comments. 146K subscribers in the C_Programming community. The subreddit for the C programming language
