Re: [OT - welcome msg]

From: osmium (r124c4u102_at_comcast.net)
Date: 01/02/04 

Date: Fri, 2 Jan 2004 12:57:44 -0800

Christopher Benson-Manica writes:

> golson <golson@worldnet.att.net> spoke thus:
>
> > I have written a C function to copy a flash write routine that is in
> > Flash memory to RAM memory. I have then created a function that
> > uses a Function Pointer to run the copied function in RAM.
>
> > etc.
>
> (The below welcome text was originally written by Ben Pfaff)

There must be a better phrase than "Welcome message" for a message that says
"Get the hell out of here". This is not in keeping with the avowed intent
of the owners of this newsgroup of being precise.

>
> Your question is outside the domain of comp.lang.c, which discusses
> only the standard C programming language, including the standard C
> library. This is a remarkably narrow topic compared to what many
> people expect.
>
> For your convenience, the list below contains topics that are not
> on-topic for comp.lang.c, and suggests newsgroups for you to explore
> if you have questions about these topics. Please do observe proper
> netiquette before posting to any of these newsgroups. In particular,
> you should read the group's charter and FAQ, if any (FAQs are
> available from www.faqs.org and other sources). If those fail to
> answer your question then you should browse through at least two weeks
> of recent articles to make sure that your question has not already
> been answered.
>
> * OS-specific questions, such as how to clear the screen,
> access the network, list the files in a directory, or read
> "piped" output from a subprocess. These questions should be
> directed to OS-specific newsgroups, such as
> comp.os.ms-windows.programmer.misc, comp.unix.programmer, or
> comp.os.linux.development.apps.
>
> * Compiler-specific questions, such as installation issues and
> locations of header files. Ask about these in
> compiler-specific newsgroups, such as gnu.gcc.help or
> comp.os.ms-windows.programmer.misc. Questions about writing
> compilers are appropriate in comp.compilers.
>
> * Processor-specific questions, such as questions about
> assembly and machine code. x86 questions are appropriate in
> comp.lang.asm.x86, embedded system processor questions may
> be appropriate in comp.arch.embedded.
>
> * ABI-specific questions, such as how to interface assembly
> code to C. These questions are both processor- and
> OS-specific and should typically be asked in OS-specific
> newsgroups.
>
> * Algorithms, except questions about C implementations of
> algorithms. "How do I implement algorithm X in C?" is not a
> question about a C implementation of an algorithm, it is a
> request for source code. Newsgroups comp.programming and
> comp.theory may be appropriate.
>
> * Making C interoperate with other languages. C has no
> facilities for such interoperation. These questions should
> be directed to system- or compiler-specific newsgroups. C++
> has features for interoperating with C, so consider
> comp.lang.c++ for such questions.
>
> * The C standard, as opposed to standard C. Questions about
> the C standard are best asked in comp.std.c.
>
> * C++. Please do not post or cross-post questions about C++
> to comp.lang.c. Ask C++ questions in C++ newsgroups, such
> as comp.lang.c++ or comp.lang.c++.moderated.
>
> * Test posts. Please test in a newsgroup meant for testing,
> such as alt.test.
>
> news.groups.questions is a good place to ask about the appropriate
> newsgroup for a given topic.
>
> --
> Christopher Benson-Manica | I *should* know what I'm talking about - if I
> ataru(at)cyberspace.org | don't, I need to know. Flames welcome.

Relevant Pages

  • Re: [OT] Mystery: static variables & performance
    ... >> This newsgroup discusses the ISO standard C language. ... This standard *defines* the C language which is the topic of this ... > enlightened suggestions through responses and private emails. ...
    (comp.lang.c)
  • Re: [FAQs, links] Off Topic: Stack vs. Heap
    ... >> so that we can redirect to to the appropriate newsgroup. ... (local variables), 'static' (file scope variables, ... That's what the 'standard' is all about. ...
    (comp.lang.cpp)
  • Re: curious about array initialization.
    ... programming language other than C what they think of this definition. ... It's the definition in the C standard. ... The C language is what we discuss in this newsgroup. ... with things not defined by the ISO C standards. ...
    (comp.lang.c)
  • Re: how many RAM for WinXPe ?
    ... read data from custom PCI boards and write to hard drive, ... >>> What I wonder is how many RAM memory is needed for a basic WinXPe, ... >>> same as a standard WinXP on a desktop? ...
    (microsoft.public.windowsxp.embedded)
  • Re: How often do you read the C standard?
    ... people on this newsgroup supposedly get paid to write professionally. ... but when I think of a strictly conforming ISO ... you need to deviate from the standard to get ...
    (comp.lang.c)
Loading