Yanked by Microsoft

[shankle]

Way Back I purchased Microsoft's MASM. Then they stopped supporting it.
Now they are executing the final blow by crippling ML.exe.
I am now using Hutche's MASM32. With the crippling of the proposed ML.exe
I think MASM32 will die.
All through my programming life I have had languages crammed down my thoat that I don't like.
Sorry for the tirade.

Question?
Am I right in assuming GOASM doesn't have this problem? It has it's own equivalent of ML.exe????
JPS

[drhowarddrfine]

Well, hutch's version IS ml.exe GoAsm is independently developed.

[donkey]

GoAsm has nothing at all to do with Microsoft or MASM, GoTools is one of the few complete assembly packages, with a dedicated linker and resource compiler as well as it's own debugger. Though MASM users may find that GoAsm users tend to have a different view as to what high level constructs are necessary.

As Doc said, the MASM32 package is simply a set of tools, libraries and macros for the Microsoft Macro Assembler, it is not an assembler in it's own right.

[MusicalMike]

What do you mean when you say Microsoft is crippling ML.exe?

[zooba]

The 64-bit version of ML seems likely to not have some of the high-level constructs which exist at present. Last I heard on the issue 'INVOKE' and 'PROC' had been reinstated but the runtime conditionals (ie. .IF, .WHILE, etc) were being removed.

Luckily, POASM will contain most of these :U