构建错误：＆QUOT;一名前pression过长或复杂的编译＆QUOT; [英] Build error: "An expression is too long or complex to compile"

问题描述

每一个现在，然后当我建立一个具体的解决方案，我会得到一个随机的一名前pression过长或复杂的编译，在错误列表窗口。不过，唯一的项目错误指的是具体的项目，该项目中没有一个文件或一个特定的LOC。

Every now and then when I build a specific solution, I'll get a random amount of "An expression is too long or complex to compile" in the Error List window. However, the only item the error points to is the specific project, not a file within the project or a specific LOC.

当我遇到这样的，我'干净'，然后我重新启动VS和这似乎解决它。是什么原因造成这种任何想法？

When I encounter this, I 'Clean' and then I restart VS and that seems to fix it. Any ideas on what is causing this?

这特殊的解决方案有50个项目在里面。

This particular solution has 50 projects in it.

推荐答案

仅供参考，这一错误是跑出来的堆栈空间编译器的性能。通常情况下，当你在编译器抛出一个深递归的问题发生，就好说了，

FYI, that error is characteristic of the compiler running out of stack space. Typically that happens when you throw a "deep recursion" problem at the compiler, like say,

int x = (1 + (1 + (1 + (1 + ......... + 1 ) + 1 ) + 1 ) + 1);

说，数千名深。句法和语义分析都是递归下降分析仪，因此容易出现极端的情况下运行的堆栈空间。

say, several thousand deep. The syntactic and semantic analyzers are both recursive-descent analyzers and therefore prone to running out of stack space in extreme scenarios.

我不知道为什么关机和启动过会影响，虽然。这真是奇怪。

I have no idea why shutting down and starting over would affect that, though. That is really strange.

如果你得到一个坚实的摄制，我很乐意看到它。无论它张贴在这里，或者输入上连接一个错误，我们将看看它。如果没有一个坚实的摄制，虽然这是很难说什么是怎么回事。

If you get a solid repro, I'd love to see it. Either post it here, or enter a bug on Connect and we'll have a look at it. Without a solid repro though it is very hard to say what is going on here.

这篇关于构建错误：＆QUOT;一名前pression过长或复杂的编译＆QUOT;的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！