FAQ还是FAQ？ [英] FAQ or not FAQ?
问题描述
你好。
这个组的欢迎信息说：
" comp.lang.c ++ FAQ可在<
http://www.parashift.com/c++-faq-lite/"
然而，该常见问题解答中没有提到这个新闻组的常见问题解答，它
称自己为C ++ FAQ Lite。关于[] []
用法和过去其他人的当前帖子显示，有问题的文件不会反映团体的共识，因此不好玩这个角色
的小组常见问题。
所以我认为引用的段落必须重写才能不说
或给人的印象是C ++ FAQ Lite是comp.lang.c的常见问题解答。
也许我们需要一个只有一点的常见问题解答：是''' C ++ FAQ Lite'的常见问题解答
comp.lang.c ++？" ;-)
-
Salu2
$ b $bJuliánAlbo写道：
你好。
这个组的欢迎信息说：
" comp.lang.c ++ FAQ可在
http://www.parashift.com/c++-faq-lite/"
但是，该常见问题解答中没有提到这个新闻组的常见问题解答，它是b / b自称为C ++ FAQ Lite。关于[] []
用法和过去其他人的当前帖子显示，有问题的文件不会反映团体的共识，因此不好玩这个角色
的小组常见问题。
所以我认为引用的段落必须重写才能不说
或给人的印象是C ++ FAQ Lite是comp.lang.c的常见问题解答。
也许我们需要一个只有一点的常见问题解答：是''' C ++ FAQ Lite'的常见问题解答
comp.lang.c ++？" ;-)
此组未经审核。任何人都可以进来并声称已经写了新闻组常见问题解答。没有其他人加强的事实
并且不断被这个小组的成员用来回答问题
在其中发现它反映了小组的共识。
事实上，有几个人对于一个特定的
常见问题非常大声地不同意这一点并没有改变这一点。
JuliánAlbo写道：
该组的欢迎辞中写道：
" comp.lang.c ++常见问题解答可以在
http://www.parashift.com/c++-faq-lite/"
但是，这个常见问题解答中没有提到这个新闻组的常见问题，
它自称为C ++ FAQ Lite。目前关于
[] []用法的帖子以及其他人在过去表明
问题中的文件没有反映出该组的共识，因此
不能很好地发挥团队常见问题的作用。
所以我认为引用的段落必须重写以便
不说或给人的印象是C ++ FAQ Lite是常见问题解答
comp.lang.c ++
也许我们只需一个FAQ point：是''C ++ FAQ Lite''
comp.lang.c ++的常见问题解答？" ;-)
在大多数情况下，C ++ FAQ Lite列表（由Marshall Cline维护）
在c.l.c ++中反映了常见问题。至于答案，他们可以更改
，联系Marshall Cline。至于欢迎
消息，它是为了方便起见，并且确实反映了关于考虑c.l.c ++ FAQ，IMO的共识
。但我们会看到，我猜...
V
-
请删除大写''A'在回复电子邮件时
我没有回复最热门的回复，请不要问
*JuliánAlbo ：
你好。
这个组的欢迎信息说：
" comp.lang.c ++常见问题解答可在
http://www.parashift.com/c++-faq-lite/"
但是，该常见问题解答中没有提到这个新闻组的常见问题解答，它将b / b称为C ++ FAQ Lite。关于[] []
用法和过去其他人的当前帖子显示，有问题的文件不会反映团体的共识，因此不好玩这个角色
的小组常见问题。
所以我认为引用的段落必须重写才能不说
或给人的印象是C ++ FAQ Lite是comp.lang.c的常见问题解答。
也许我们需要一个只有一点的常见问题解答：是''' C ++ FAQ Lite'的常见问题解答
comp.lang.c ++？" ;-)
确切地说，它是[comp.lang.c ++。moderated]的常见问题解答;见< url：
http://www.gotw.ca/resources/clcm.htm> ;.
但是作为[comp。的常见问题解答]。 lang.c ++。moderated]它也适用于[comp.lang.c ++]的
常见问题。
除非我有我的历史完全错了，它成了
[comp.lang.c ++。moderated]的FAQ，因为它被广泛认为是
的常见问题[comp.lang.c ++并且毫不奇怪，它仍然被广泛认为是[comp.lang.c ++]的常见问题解答。但是当然对于这个没有主持人的团体来说，这只是集体思维中的所有内容;-)，这完全取决于
社区的认可。如果说，马歇尔出于某种原因无法维持
常见问题解答，而其他人接手，并且常见问题已退化，而且足够的
我们开始提及其他一些常见问题解答（如果有的话，那就是很多
连接），那么其他常见问题解答就是这个小组的常见问题，或者
也许我们'然后有两个或更多质量的常见问题解答，如当前，然后
然后可能[comp.lang.c ++。moderated]会效仿。
-
答：因为它弄乱了人们通常阅读文字的顺序。
问：为什么这么糟糕？
A：热门发布。
问：usenet和电子邮件中最烦人的事情是什么？
Hello.
The welcome message of this group says:
"The comp.lang.c++ FAQ is available at
http://www.parashift.com/c++-faq-lite/"
However, nothing in that FAQ mentions that is FAQ of this newsgroup, it
calls itself "the C++ FAQ Lite". And the current thread about the [ ] [ ]
usages and others in the past shows that the document in question does not
refelect the consensus of the group, and thus does not play well the role
of FAQ of the group.
So I think that the quoted paragraph must be rewritten in order to not say
or give the impression that the C++ FAQ Lite is the FAQ of comp.lang.c++
Maybe we need a FAQ with just one point: "Is ''The C++ FAQ Lite'' the FAQ of
comp.lang.c++?" ;-)
--
Salu2
Julián Albo wrote:Hello.
The welcome message of this group says:
"The comp.lang.c++ FAQ is available at
http://www.parashift.com/c++-faq-lite/"
However, nothing in that FAQ mentions that is FAQ of this newsgroup, it
calls itself "the C++ FAQ Lite". And the current thread about the [ ] [ ]
usages and others in the past shows that the document in question does not
refelect the consensus of the group, and thus does not play well the role
of FAQ of the group.
So I think that the quoted paragraph must be rewritten in order to not say
or give the impression that the C++ FAQ Lite is the FAQ of comp.lang.c++
Maybe we need a FAQ with just one point: "Is ''The C++ FAQ Lite'' the FAQ of
comp.lang.c++?" ;-)This group is not moderated. Anyone can come in here and claim to have
written the newsgroup FAQ. The fact that nobody else has stepped up
and it keeps getting used by members in this group to answer questions
found within it show that it DOES reflect the concensus of the group.
The fact that a few people disagree very loudly about one particular
FAQ in it doesn''t change this.
Julián Albo wrote:The welcome message of this group says:
"The comp.lang.c++ FAQ is available at
http://www.parashift.com/c++-faq-lite/"
However, nothing in that FAQ mentions that is FAQ of this newsgroup,
it calls itself "the C++ FAQ Lite". And the current thread about the
[ ] [ ] usages and others in the past shows that the document in
question does not refelect the consensus of the group, and thus does
not play well the role of FAQ of the group.
So I think that the quoted paragraph must be rewritten in order to
not say or give the impression that the C++ FAQ Lite is the FAQ of
comp.lang.c++
Maybe we need a FAQ with just one point: "Is ''The C++ FAQ Lite'' the
FAQ of comp.lang.c++?" ;-)In most cases the "C++ FAQ Lite" list (maintained by Marshall Cline)
acurately reflects the FAQ in c.l.c++. As to the answers, they can
be changed, contact Marshall Cline for that. As to the Welcome
message, it''s here for convenience, and does reflect the consensus
about what to consider c.l.c++ FAQ, IMO. But we''ll see, I guess...
V
--
Please remove capital ''A''s when replying by e-mail
I do not respond to top-posted replies, please don''t ask
* Julián Albo:Hello.
The welcome message of this group says:
"The comp.lang.c++ FAQ is available at
http://www.parashift.com/c++-faq-lite/"
However, nothing in that FAQ mentions that is FAQ of this newsgroup, it
calls itself "the C++ FAQ Lite". And the current thread about the [ ] [ ]
usages and others in the past shows that the document in question does not
refelect the consensus of the group, and thus does not play well the role
of FAQ of the group.
So I think that the quoted paragraph must be rewritten in order to not say
or give the impression that the C++ FAQ Lite is the FAQ of comp.lang.c++
Maybe we need a FAQ with just one point: "Is ''The C++ FAQ Lite'' the FAQ of
comp.lang.c++?" ;-)To be precise, it is the FAQ of [comp.lang.c++.moderated]; see <url:
http://www.gotw.ca/resources/clcm.htm>.
But as the FAQ of [comp.lang.c++.moderated] it serves well also as the
FAQ of [comp.lang.c++].
And, unless I''ve got my history entirely wrong, it became the FAQ of
[comp.lang.c++.moderated] because it was widely recognized as the FAQ of
[comp.lang.c++], and not surprisingly it''s still widely recognized as
the FAQ of [comp.lang.c++]. But of course for this non-moderated group
it''s all in the group mind ;-), it''s all about recognition by the
community. If, say, Marshall for some reason was unable to maintain the
FAQ, and someone else took over, and the FAQ degenerated, and enough of
us then started referring to some other FAQ (that''s a lot of
concatenated if''s), then that other FAQ would be this group''s FAQ, or
perhaps we''d then have two or more FAQs of quality like the current, and
then probably [comp.lang.c++.moderated] would follow suit.
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
这篇关于FAQ还是FAQ？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
