I'm writing a GUI for NASM using Visual Basic. It works by when I click the "compile" button it writes a batch file that performs all the needed steps to both assemble and link the EXE file, and then issues the DEL command to delete the batch file. Because I'm trying to avoid calling up any console windows, I'm using the > operator in the batch file (so I can read any output later if needed). When used in the commandline console for Windows (which emulates a dos screen), or when using a batch (*.bat) file, the > operator is supposed to redirect any text that normally appears in the console to an output file, which is specified immediately after the > operator. So for example, if I run this command "nasm.exe /f win32 myprog.asm>nasm_log.txt" it is supposed to redirect any console output (such as errors, progress messages, etc) to the file "nasm_log.txt". But it doesn't work. I don't know how, but NASM was apparently programmed in such a way that its console output avoids being redirected to a file with the > operator, which causes the text to still appear in the console, and the resulting text file from the > operator ends up being an empty file. If this is intentional, this is extremely horrible programming practice. Console output should ALWAYS be redirectable with the > operator. If this is simply a bug, it is a bug that requires IMMEDIATE attention. I seriously hope that the NASM development team reads these forums, and learns about bugs that need fixing via reading these forums.
