CompuServe Thread

#Assm Recommd

5 messages in this thread
#26318From: James GreenJul 29, 1992 9:17 PM
I'm looking to buy a new assembler? Any recommendations? Does anybody know about what is happening with DevPac, will the author try to release a new version? Was there an author or was it Michtron? I'm running an A3000 with 8 megs. Thanx -James -via My own fingers
#26340From: David OldisJul 31, 1992 2:18 AM
James… I have no idea as to what assembler to get. For me its "the cheaper the better" <smile>. Goodluck tho… David
#26354From: ShraddhanJul 31, 1992 4:18 PM
James, DevPac version 3 came out not that long ago. It has a vastly improved editor (multiple files, multiple windows on the same file, bookmarks) compared with version 2. The only flaw with the new editor is that it doesn't show the line number and column number. The assembler is also much improved. From what I've heard, DevPac 3 is THE assembler to go for. It's GREAT! BTW version 3 now supports WB 2.0x (at last). Regards, Shraddhan – via Whap! from Hertfordshire in the UK
#26824From: New memberAug 13, 1992 10:27 PM
No line numbers? Ack! What do you do about error messages. Syntax error in line 1082 could get a mite tiffy. How about a MACRO key? Those are the two MUST haves for me. Oh and multiple files open. So you can cut and paste. The old TxEd works "ok" for me. I use an external Macro keys program to make me happy.
#27239From: ShraddhanAug 22, 1992 10:01 PM
Jay, Having been away on holiday for the last few weeks, I don't quite remember what I might have said. Seems like I was describing the editor in the HiSoft Devpac assembler. I'm rather miffed (and surprised) that line numbers are no longer shown on screen – you have to press the 'HELP' key to find out what line number you are on. However, as for error messages, the assembler scrolls the display to the appropriate line, if the file concerned happens to be in memory at the time; plus you also have a 'go to line number' command. So you can be assembling code made up of three source files, two of which you are working on and therefore have in memory, while the third remains on disk. When you get an error in one of the first two files, the editor shows you the relevant line automatically (in the relevant file), and gives you a message like 'error in line 12345 in file part3.asm' where you do indeed have to write down the line number and file name, load the file, and go to that line, all by hand with no help. This is no big deal, as you can always re-assemble with the file in memory, and have the editor/assembler help you out. And the editor _does_ have a MACRO key capability, not that I use it much. And it has the capability of having multiple windows on the same file, something which is occasionally invaluable. I believe I tried TxEd some time ago, found that it seemed to offer me nothing that I felt I needed and didn't already have, and forgot about it as I didn't have a hard disk at that time and didn't want too many floppies to mislay on my desk. Besides, having the editor, assembler and debugger integrated as if they were a single package is just great. Regards, Shraddhan – via Whap! from Hertfordshire in the UK