返回列表 发帖
原帖由 寄托天下 于 2007-4-20 10:51 发表 http://bbs.ioage.com/images/common/back.gif
Your suggestion sounds like a poem,maybe I would call mentalism. lol.Of cz its a joke.But u know that  if the debugversion have been put in 2 someguys should be destroy the users' confidence of t ...



It doesn't necessarily follow.
I don't know what is "Mathon debug version  blood event", but if use the proper policy, the debug version would contribute the trail of some damn bug and not severely reduce the experience.
I'm a developer, "OutputDebugString" is the usual debug method. From the msdn(http://msdn2.microsoft.com/en-us/library/aa363362.aspx), we learn:
If the application has no debugger, the system debugger displays the string. If the application has no debugger and the system debugger is not active, OutputDebugString does nothing.

OutputDebugString function is thread safe, we can view the pseudocode from http://www.unixwiz.net/techtips/OutputDebugString.txt. As far as I know a lot of software productions use the function in the release version at some time in the past. Such as TM, NAV, MSDN etc(Maybe skip over to remove).

If use OutputDebugString , we can receive the debug string info only by use some debug tools such as Debugview(http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx) . As normal user, get nothing. Moreover, it don't generate any file in the disk.

TOP

返回列表