"Dan Kegel" <d...@kegel.com> wrote: >>> Compiling DOS code to a .com file will produce a very small >>> executable, then embedding it into the test, put it in %TEMP%, >>> and exec should be trivial. No need for external tools IMO. >> >> I thought of that, it's tempting. >> >> But nasm is pretty common; I don't know that it would >> really be a burden to use it. And it would help testcase >> readability. > > and/or maintainability. Nobody likes having binary blobs > next to the source code they supposedly came from.
The exception tests in ntdll is a nice example how to do that without hurting readability and maintainability. -- Dmitry.