----- Original Message -----
From: "Oliver Kowalke"
The only real problem that I'm aware of is MinGW, which you should support directly anyway. See https://svn.boost.org/trac/boost/ticket/7262 which (a) describes a concrete use case where your proposed solution of using masm cannot possibly work, and (b) includes a patch.
that's the problem! - MinGW's assembler tool does have a different syntax than MASM. The defacto standard on Windows is MASM - why not use the standard tool on the platform to compile the object files (boost.context consists of assembler only). why must be the different assembler syntax' of the different assembler tools be supported?
I am no expert when it comes to assembler variations, but I'd rather not have to have a dependency on MS tools. VC++ et al being the "standard tools on the platform" is part of the problem, not something to be encouraged. Regards, Paul Mensonides