MASM documentation
in [MFC]
|
Prev: using CList as a base class in an extension DLL
Next: Left/Right keys don't work in CDockablePane
From: Giovanni Dicanio on 14 Nov 2009 10:07 "Joseph M. Newcomer" <newcomer(a)flounder.com> ha scritto nel messaggio news:mebsf590t5c7h1q5ugnnobdnb0024i8udj(a)4ax.com... > It is surprising how horribly bad the documentation is. [...] > I thought writing a course in using MASM would be easy. It probably would > be, if there > were any documentation. Right now, I have to run experiments. Joe: I'm not sure if this helps, but I found the Art of Assembly Language book freely available online: http://webster.cs.ucr.edu/AoA/DOS/pdf/0_AoAPDF.html And there is a chapter about MASM here: http://webster.cs.ucr.edu/AoA/DOS/pdf/ch08.pdf Giovanni
From: Joseph M. Newcomer on 14 Nov 2009 10:14 I almost certainly have one in my basement, but this week I am nearly immobilized by pain (did something to tear a ligament in my leg) so walking downstairs to find it...and standing while I dug around in the old boxes...wasn't really an option. Maybe after I get back next week (I'm off for a week of teaching tomorrow) I'll be able to go down and get it. joe On Fri, 13 Nov 2009 22:49:01 -0800, Geoff <geoff(a)invalid.invalid> wrote: >On Fri, 13 Nov 2009 23:33:56 -0500, Joseph M. Newcomer ><newcomer(a)flounder.com> wrote: > >>It is surprising how horribly bad the documentation is. > >I dug around my bookshelves and finally came up with the MASM book I >got with my original Windows SDK. (the big blue and white box) > >Title: Microsoft Macro Assembler 5.1 Programmer's Guide >Copyright: 1987 >Document number: 410610014-500-R00-0787 >467 pages. > >No bar code, the back has the MS Redmond address and is marked >1287 Part No. 01506 > >This was my only reference for it for years. You might find a copy of >it on amazon.com. The online copies I cited in my other post actually >get to the nitty gritty a bit more succinctly in the 6.11 >documentation and they are more relevant today. Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: Tom Serface on 14 Nov 2009 10:17 I've had that happen to me as well, but since I've upgraded to Office 2007 I haven't had any problems (except installing VS 2008 SP1 which won't work with the Web Designer installed so I had to rename that folder and remove some registry entries). I'll never get that 5 hours back it took me to finally get programs to compile on my notebook and run on my desktop with the same versioning. Although, to be fair, I learned a lot about manifest and winsxs in the process. You'd think some of the testing would have included trying a few "other" products from the same company to ensure that they all play together well. Tom "David Ching" <dc(a)remove-this.dcsoft.com> wrote in message news:%23%233tf6IZKHA.2160(a)TK2MSFTNGP02.phx.gbl... > "Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message > news:g24rf5hvuo3qbgjmj6kmrefapvsc8gdice(a)4ax.com... >> Has anyone ever encountered the documentation for MASM. Not the useless >> garbage in the >> MSDN, but real documentation. THe kind that gives the syntax of >> identifiers, for example, >> or explains what options are available with the OPTIONS directive (not >> just a list of >> them, but the actual explanations)? Or the syntax of a string, or of an >> initializer? >> > > I suggest you download MASM from your MSDN subscription because it comes > with a set of .doc files describing all kinds of stuff. But if you are > using Word 2003/2007, these ancient files are blocked by default, and I > had to edit the registry in order to get the modern Word to open them > (something about security....) Security by feature removal, yeah, that's > the ticket! :-O > > -- David
From: Tom Serface on 14 Nov 2009 10:17 But, I can read any documents at all now that I have Office 2007 installed. Tom "David Ching" <dc(a)remove-this.dcsoft.com> wrote in message news:%23%233tf6IZKHA.2160(a)TK2MSFTNGP02.phx.gbl... > "Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message > news:g24rf5hvuo3qbgjmj6kmrefapvsc8gdice(a)4ax.com... >> Has anyone ever encountered the documentation for MASM. Not the useless >> garbage in the >> MSDN, but real documentation. THe kind that gives the syntax of >> identifiers, for example, >> or explains what options are available with the OPTIONS directive (not >> just a list of >> them, but the actual explanations)? Or the syntax of a string, or of an >> initializer? >> > > I suggest you download MASM from your MSDN subscription because it comes > with a set of .doc files describing all kinds of stuff. But if you are > using Word 2003/2007, these ancient files are blocked by default, and I > had to edit the registry in order to get the modern Word to open them > (something about security....) Security by feature removal, yeah, that's > the ticket! :-O > > -- David
From: Joseph M. Newcomer on 14 Nov 2009 10:16
When MASM was developed, computers barely existed. We had to walk barefoot through the snow to get our listings... joe On Sat, 14 Nov 2009 13:41:15 +0100, "Giovanni Dicanio" <giovanniDOTdicanio(a)REMOVEMEgmail.com> wrote: >"Joseph M. Newcomer" <newcomer(a)flounder.com> ha scritto nel messaggio >news:mebsf590t5c7h1q5ugnnobdnb0024i8udj(a)4ax.com... > >> It is surprising how horribly bad the documentation is. >> MASM doesn't support Unicode, and I even have a slide that points this >> out; it has to be >> >> hello DB 'H', 00h, 'E', 00h, 'L', 00h, 'L', 00h, 'O', 00h, 00h, 00h >> >> I can see why companies are having problems finding people who can program >> in assembler. >> When you can't learn how something works, you won't use it. > >Probably when MASM was developed Unicode did not exist? >(I've never used this MASM, I don't know. I just used Devpac Assembler for >Motorola MC68000 on Commodore Amiga). > > >> But now they're paying the price: people who need super-high-performance >> and want to use >> the fancy MMX/XMM/etc instructions can't figure out how to use them or >> write them; > >I have no idea of the assembly of the new Intel CPUs, but I read somewhere >that writing *hand-coded* optimized assembly code is hard these days (it's >not like the age of 80286 or Motorola 68000), and optimizing C++ compilers >do a better job than humans in producing optimized assembly code. > > >>The number of us who used to earn our livings >> writing huge systems in assembly code (250K lines) is dwindling... > >Wow... Writing 250K lines of assembly code must be a titanic work (leaving >apart debugging...!). > > >> I don't really believe in writing more that tiny subroutines in assembler, >> but what I seem >> to take for granted--how to write assembly code--is apparently becoming a >> lost art. > >As is COM programming :) > > >> I thought writing a course in using MASM would be easy. It probably would >> be, if there >> were any documentation. Right now, I have to run experiments. > >Have fun :) > > >Giovanni > Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm |