Why foo and bar in every tutorial i read?

[Arndt Jonasson]

The first thing you learn when you go to law school is that any set of
words can be interpreted to mean whatever you like. That's why the cases
are always won by the side with the best lawyer(s) - i.e., the side with
the most money.

So it is here. The so-called "regulars" will gladly agree that the topic
here is "C". It's just that they define the term and the auxilliary
concepts so narrowly as to be absurd. You will learn to live with it.

Well, I didn't ask in order to learn what the group is about - I've
read it long enough (*). It looked like some were saying that
"discussion about C" was something the stupid google people had made
up, and altogether wrong, so I tried to find where it came from, and
it's actually fine.

I haven't read comp.lang.c continously the last few years. When I
looked last, the atmosphere was very much more acrimonious, with some
people seemingly delighting in telling people off, including jumping
on people who tried to clear things up. Now I like it much better -
the main bully character has apparently left, and there are several
who give very nice and informative answers to all reasonable
questions, including off-topic ones. You know who you are, keep up
the good work!

(*) Though there were no comp.std.c or compiler-specific groups in 1984.

As for asking about "foo" and "bar" here, it's off-topic, but where do
you ask? I can't name a group off the top of my head where it would be
on-topic.

 

[Dik T. Winter]

>
> I view comp.std.c as being, metaphorically if not literally, the result
> of a "split", and thus some of the topics for net.lang.c go there
> instead of here. I'd have to look up what happened to get comp.std.c
> created to figure out if i'm actually right.

At the same time you might look up what happened to get comp.programming
created.

 

[Mark L Pappin]

As for asking about "foo" and "bar" here, it's off-topic, but where do
you ask?

alt.folklore.computers

mlp