OceanMachine wrote:
OutputDebug?
OutputDebug outputs to a debugger via
OutputDebugString if one is attached to the current process. Tools like DbgView can catch it, as can Visual Studio if you're debugging AutoHotkey.exe (useful only to developers like myself). It doesn't output to stderr.
wtg wrote:
It's interesting that the #ErrorStdOut parm lets us redirect STDERR to STDOUT,
Don't be misled by the name; it has nothing to do with stderr:
Quote:
Sends any syntax error that prevents a script from launching to stdout rather than displaying a dialog.
Source: #ErrorStdOut Quote:
Regarding the fincs thread, if I understand it correctly, he's made some modifications to the _L release so OutputDebug will output to STDERR that can then be used by SciTE debugger.
fincs statement is easily misinterpreted. He was referring specifically to the "
stderr" DBGp command, which is ordinarily intended for redirecting the stderr stream to a DBGp (debugger) client. In our case, AutoHotkey doesn't make use of the stderr stream, so fincs repurposed the "stderr" command for redirecting OutputDebug to the DBGP client. The actual stderr stream is not involved.
Try this:
Code:
StdErr_Write("hello, world!")
StdErr_Write(text) {
if A_IsUnicode
; Note: StrLen(text) might be incorrect if multi-byte characters are involved:
return StdErr_Write_("astr", text, StrLen(text))
return StdErr_Write_("uint", &text, StrLen(text))
}
StdErr_Write_(type, data, size) {
static STD_ERROR_HANDLE := -12
if (hstderr := DllCall("GetStdHandle", "uint", STD_ERROR_HANDLE)) = -1
return false
return DllCall("WriteFile", "uint", hstderr, type, data, "uint", size, "uint", 0, "uint", 0)
}
Login
Register
FAQ
Search
