| 12764 | } |
| 12765 | |
| 12766 | ResultType Line::LineError(LPCTSTR aErrorText, ResultType aErrorType, LPCTSTR aExtraInfo) |
| 12767 | { |
| 12768 | ASSERT(aErrorText); |
| 12769 | if (!aExtraInfo) |
| 12770 | aExtraInfo = _T(""); |
| 12771 | |
| 12772 | if (g_script.mIsReadyToExecute) |
| 12773 | { |
| 12774 | return g_script.RuntimeError(aErrorText, aExtraInfo, aErrorType, this); |
| 12775 | } |
| 12776 | |
| 12777 | if (g_script.mErrorStdOut && aErrorType != WARN) |
| 12778 | { |
| 12779 | // JdeB said: |
| 12780 | // Just tested it in Textpad, Crimson and Scite. they all recognise the output and jump |
| 12781 | // to the Line containing the error when you double click the error line in the output |
| 12782 | // window (like it works in C++). Had to change the format of the line to: |
| 12783 | // printf("%s (%d) : ==> %s: \n%s \n%s\n",szInclude, nAutScriptLine, szText, szScriptLine, szOutput2 ); |
| 12784 | // MY: Full filename is required, even if it's the main file, because some editors (EditPlus) |
| 12785 | // seem to rely on that to determine which file and line number to jump to when the user double-clicks |
| 12786 | // the error message in the output window. |
| 12787 | // v1.0.47: Added a space before the colon as originally intended. Toralf said, "With this minor |
| 12788 | // change the error lexer of Scite recognizes this line as a Microsoft error message and it can be |
| 12789 | // used to jump to that line." |
| 12790 | g_script.PrintErrorStdOut(aErrorText, aExtraInfo, mFileIndex, mLineNumber); |
| 12791 | return FAIL; |
| 12792 | } |
| 12793 | |
| 12794 | return g_script.ShowError(aErrorText, aErrorType, aExtraInfo, this); |
| 12795 | } |
| 12796 | |
| 12797 | ResultType Script::RuntimeError(LPCTSTR aErrorText, LPCTSTR aExtraInfo, ResultType aErrorType, Line *aLine, Object *aPrototype) |
| 12798 | { |
no test coverage detected