老刘

> Hi @OldLiu001 > > Congrats to you for making your own VBScript implementation. > > I made a pull request (#640) which enable the `runtest.py` script to run mal...

@kanaka Thank you for your advice. I just tried the following: - Restore `runtest.py` to the unupdated version. - Install an WSL on my local machine. - Test `runtest.py` with...

@kanaka I did the following tests: - Use the unupdated version of `runtest.py`. - Retest the vbs impl to get the log file. - Test the bash impl in WSL...

Let me briefly summarize the above discussion: - According to my previous discussion with @cy20lin in #640, the `runtest.py` modified by @cy20lin has been fully tested on the Windows platform,...

@kanaka Regarding the structural changes you mentioned in merging 'EvaluateAST' and 'MacroExpand' into 'Evaluate', I went to #587 , and since it's been a long time since I finished my...

@kanaka I did the following tests: - Use `runtest.py` you lately provided. - Run `make "test^vbs^step0"`, it passed all the test smoothly. - Run `make "test^vbs^step1"`, I test it many...

> If it's still broken, I would be interested in the the same debug output from vbscript and bash as before. I'm pretty confident that we can get this to...

@kanaka Thank you for your precise point of view. I wrote `test_stderr_buffered.mal` for testing: ``` $ cat test_stderr_buffered.mal "a" (1 2 "c" $ cscript.exe -nologo step1_read_print.vbs < test_stderr_buffered.mal user> "a"...

I avoided the buffered stderr problem by introducing `cmd.exe` as a mediator and merging the error output stream into the standard output stream within it. `impls/vbs/run` ``` #!/bin/bash cmd.exe /c...

@kanaka The `WSL` environment on `Github Action` has been set up and the results are consistent with what I tested locally. I can already see the dawn of victory! Finally...