Transaction

6069d95bcb9953d3496e00fadb98aa7fd0714d2e2543ef8f6b78b45e15215fc5
( - )
7,038
2024-03-27 20:52:08
1
1,545 B

2 Outputs

Total Output:
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM <div class="post">I am still crunching along on the man page, it is starting to look pretty good.&nbsp; I did come across a couple of issues though.&nbsp; First, there is a "-printtodebugger" command line option.&nbsp; I added it to the "usage" information when you give -h and I also added it to the man page but I can't tell what it does by looking at the code, other than to see that it is only used on windows machines.<br/><br/>Secondly, in the process of investigating the OutputDebugStringF() function I discovered that the code has the ability to output to a console by setting the global variable fPrintToConsole to true.&nbsp; The variable, however, was initialized to false and there was no where in the code that sets it to true.&nbsp; Because of this I added a -printtoconsole which sets both this variable and fDebug to true.&nbsp; I think both should be set but I am wondering if I should leave fDebug alone.&nbsp; If I don't set it in the code then the user would have to do "-printtoconsole -debug" on the command line instead, we may or may not want this depending on whether there is more/less verbosity implied by debug but from a quick grep of the code it looks like it should be the way I currently have it where it automatically sets both variables.<br/><br/>-Buck</div> text/html
    https://whatsonchain.com/tx/6069d95bcb9953d3496e00fadb98aa7fd0714d2e2543ef8f6b78b45e15215fc5