这个 Internal error: 内部错误 给你一段Delphi 自己的帮助参考一下。 Occasionally when compiling an application in Delphi, the compile will halt and display an error message that reads, for example:Internal Error: X1234This error message indicates that the compiler has encountered a condition, other than a syntax error, that it cannot successfully process. The information after "Internal Error" contains from one to three characters and is immediately followed by a number that indicates the file and line number in the compiler itself where the error occurred. Although this information may not help you, it can help us (Borland) track down the problem if and when you report the error. Be sure to jot down this information and include it with your internal error description.What to do if you encounter an internal errorFollow these steps to attempt to resolve an internal error:1. If the error occurs immediately after you have modified code in the editor, go back to the place where you made your changes and make a note of what was changed. 2. If you can undo or comment out the change and then recompile your application successfully, it is possible that the programming construct that you introduced exposed a problem with the compiler. If so, skip to step 7. Otherwise, follow the next few steps to resolve your problem. 1. Delete all of the .dcu or .dpu files associated with your project.2. Close your project completely using File | Close All, then reopen your project, this will clear the unit cache maintained in the IDE. Alternatively you can simply close the IDE and restart. 3. Another options is to try and recompile your application using the Project|Build option so that the compiler will regenerate all of your dcus or dpus. 4. If the error is still present exit the IDE and try to compile your application using the command line version of the compiler (dcc32.exe) from a command prompt. This will remove the unit caching of the IDE from the picture and could help to resolve the problem.If the problem still exists, go back to the place where you last made modifications to your file and review the code. Typically, most internal errors can be reproduced with only a few lines of code and frequently the code involves syntax or constructs that are rather unusual or unexpected. If this is the case, try modifying the code to do the same thing in a different way. For example, if you are typecasting a value, try declaring a variable of the cast type and do an assignment first.Examplesbegin if Integer(b) = 100 then... end; var a: Integer; begin a := b; if a = 100 then... end;Here is an example of unexpected code that you can correct to resolve the error:var A : Integer; begin if Int64(Int64(A))=0 then end;In this case, the second cast of A to an Int64 is unnecessary and removing it corrects the error.If the problem seems to be a "while...do" loop, try using a "for...do" loop instead. Although this does not actually solve the problem, it may help you to continue work on your application. If this resolves the problem, it does not mean that either "while" loops or "for" loops are broken but more likely it means that the manner in which you wrote your code was unexpected. Once you have identified the problem, we ask that you create the smallest possible test case that still reproduces the error and submit it to Borland.
Internal error: 内部错误
给你一段Delphi 自己的帮助参考一下。
Occasionally when compiling an application in Delphi, the compile will halt and display an error message that reads, for example:Internal Error: X1234This error message indicates that the compiler has encountered a condition, other than a syntax error, that it cannot successfully process. The information after "Internal Error" contains from one to three characters and is immediately followed by a number that indicates the file and line number in the compiler itself where the error occurred. Although this information may not help you, it can help us (Borland) track down the problem if and when you report the error. Be sure to jot down this information and include it with your internal error description.What to do if you encounter an internal errorFollow these steps to attempt to resolve an internal error:1. If the error occurs immediately after you have modified code in the editor, go back to the place where you made your changes and make a note of what was changed.
2. If you can undo or comment out the change and then recompile your application successfully, it is possible that the programming construct that you introduced exposed a problem with the compiler. If so, skip to step 7.
Otherwise, follow the next few steps to resolve your problem.
1. Delete all of the .dcu or .dpu files associated with your project.2. Close your project completely using File | Close All, then reopen your project, this will clear the unit cache maintained in the IDE. Alternatively you can simply close the IDE and restart.
3. Another options is to try and recompile your application using the Project|Build option so that the compiler will regenerate all of your dcus or dpus.
4. If the error is still present exit the IDE and try to compile your application using the command line version of the compiler (dcc32.exe) from a command prompt. This will remove the unit caching of the IDE from the picture and could help to resolve the problem.If the problem still exists, go back to the place where you last made modifications to your file and review the code. Typically, most internal errors can be reproduced with only a few lines of code and frequently the code involves syntax or constructs that are rather unusual or unexpected. If this is the case, try modifying the code to do the same thing in a different way. For example, if you are typecasting a value, try declaring a variable of the cast type and do an assignment first.Examplesbegin if Integer(b) = 100 then...
end;
var
a: Integer;
begin
a := b;
if a = 100 then...
end;Here is an example of unexpected code that you can correct to resolve the error:var A : Integer;
begin
if Int64(Int64(A))=0 then
end;In this case, the second cast of A to an Int64 is unnecessary and removing it corrects the error.If the problem seems to be a "while...do" loop, try using a "for...do" loop instead. Although this does not actually solve the problem, it may help you to continue work on your application. If this resolves the problem, it does not mean that either "while" loops or "for" loops are broken but more likely it means that the manner in which you wrote your code was unexpected. Once you have identified the problem, we ask that you create the smallest possible test case that still reproduces the error and submit it to Borland.
现在的蝶子都是这样子呀/
我每一次delphi就要一个先的蝶子呀?
倒板者是死罪呀?
老鼠过街^^^^晕?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
spcomm是2.5版本，是不是不能在delphi5用。