本文介绍了C ++错误的详细程度的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述




为什么C ++中的编译器错误通常会如此粗糙和冗长?

为了保持这个主题,标准是否保证这一点? :)


谢谢,

Joe

Hi,

Why are compiler errors in C++ generally so friggen ugly and verbose?
To keep this on topic, does the standard guarantee this? :)

Thanks,
Joe

推荐答案




要回答你的修辞问题,这是一个实施质量问题。\\ b $ b问题。但是STLFilt的帮助很重要。


祝你好运,


Tom



To answer your rhetorical question, it''s a quality-of-implementation
issue. But STLFilt helps matters quite a bit.

Best regards,

Tom





号实际上,第86.1.5.33节,A4b小节,第1462.5段陈述

非常明确地表示然而,对于
而言,这可能是一种可靠的争论,因为这种说法可以证明其缺乏可靠性。
前面提到的不正确迹象的文字表示或

迄今为止所提出的其他不受欢迎的构造要求实施方面的合理回应确实不会失败

的贡献低于对所述

指示的最低限度可接受的理解,因此本标准的目的是

这种文本表示的实现者在所有情况下,即使在每个平台的b / b
适用的先前,现有或后续限制的情况下,也应尽量使用b $ b。努力使所述陈述简明扼要。

-not Joe


(好吧,所以我午饭吃得有点高......)



No. In fact, section 86.1.5.33, sub-section A4b, paragraph 1462.5 states
quite clearly that "Whereas it can be admitteldy arguable as to the veracity
of the claim that a demonstrable paucity of verbosity, in regards to the
aforementioned textual representation of indications of incorrectness or
other undesireable constructs heretofore presented as requiring of a
reasonable response on the part of the implementation indeed does not fail
to contribute less than a minimally acceptable understanding of said
indications, therefore it shall be the intent of this standard that
implementors of such textual representations shall, in all cases,
notwithstanding prior, existing or subsequent limitations applicable on a
per platform basis, endeavor to make said representations brief and concise.
-not Joe

(ok, so I got a little high at lunch...)





正如你所期待的那样,没有。


-

后来,

杰瑞。


宇宙是自己想象的虚构。



As, you''d expect, no.

--
Later,
Jerry.

The universe is a figment of its own imagination.


这篇关于C ++错误的详细程度的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-05 17:43