| |
tlr
Registered: Sep 2003
Posts: 1714 |
Which assemblers do you/did you use for coding?
I thought this might be interesting.
I'll start:
I started out with Hesmon, and later switched to Handics VICMON.
Never did anything major in this. Just learnt how stuff was working.
Later I bought a copy Oasis Machine Lightning (which was bought up by Ocean and turned into Laser Genious)
I used Machine Lightning for all demos I did in the 80's. Cost a shitload of money.
It's line oriented (like basic) which sucks a bit, but has very good macro facilities.
I had a quick stint with Macrofire V1.0 but thought it was cryptic.
I started using dasm as soon as I got an Amiga.
Kept on using dasm when I switched to a linux system.
I have recently started using Kick Assembler 2.12 in combination with dasm and make (under linux). |
|
... 82 posts hidden. Click here to view all posts....
|
| |
tlr
Registered: Sep 2003
Posts: 1714 |
Quote:tlr : that was the one with the red manuals? hehehe I remember it well, didn't get into it though,had the Oasis tape version.
Oasis Machine Lightning, yes. :)
The manuals where black on red pages, which was their version of copy protection... Turned up all black in copiers back then. :) |
| |
Warnock
Account closed
Registered: Sep 2007
Posts: 27 |
I used Turbo Assembler for all my coding.
I didn't have time to check out any others.
TASS was home for me.
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11115 |
petmon->smon->ar6 (huge break) tass->verious cross assemblers->cc65/acme/codenet
and i always love to read this: crossbow still uses SMON, exclusivly :) |
| |
raven
Account closed
Registered: Jan 2002
Posts: 137 |
Started with built-in monitor of a custom cartridge called
Jaguar back in 1987. Its still the only ML monitor I use.
Moved to TASM in late 1989 after joining The Force
and visiting Guy Shavitt's place.
It just seemed so easy :)
Still use a customized TASM on the 64 exclusively, no
cross-assemblers for me, kills the C64 feeling imho.
@Oswald: when I needed to insert an instruction I just
jmped to another address, executed that instruction (or
instructions) then jumped back.
That resulted in a very messy code. Very. |
| |
Starfox
Registered: Jul 2014
Posts: 31 |
Sorry for necro :)
I used Smon-EX (can't remembers spelling) which was of course, a monitor.
To answer Oswald: If you need to insert something in the middle of code, you just place a JMP there, do your stuff and JMP back 😂
I made my first intros and demos using this monitor, lol!
Now I use KickAssembler, but I don't use much of its smart features, and I don't like the // for comments, so might try our 64TASS or something. |
| |
Bansai
Registered: Feb 2023
Posts: 34 |
In the past year or so, I've become a fan of cross assemblers under Linux because of their speed, but also because for any nontrivial project, I'm writing C code as some sort of tool or emulator instrumentation anyway.
In the beginning though, a Fastload cartridge and a notebook of paper all the way. :-) |
| |
DeMOSic
Registered: Aug 2021
Posts: 126 |
Started coding around 1.5 years ago, and when i first started, i either got introduced, recomended, or just had it downloaded on my computer, to 64tass and i still use it.
Huh, i still havent updated it for some abnormal reason... maybe i should.
But now i also use Kickassembler a bit (usually when im coding something that requires speedcode such as a plasma.). |
| |
Fungus
Registered: Sep 2002
Posts: 617 |
Turbo assembler, tass64 and Action Replay monitor.
kickass and ca65 are nice, but too complex for my needs. But then I'm not a demo coder anymore. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1378 |
I'm sure there's a newer version of this thread somewhere in which I talk about using xa for small projects, ca65 for bigger ones, but in any case I've pretty much transitioned to ca65 now. New projects just start with duplicating some boilerplate, so I don't have to worry about the setup cost anymore.
That said, BitPickler 1.0.0 internally uses a 'just the features I needed for this project' assembler library I cobbled together in Rust, to avoid any external dependencies or assembler version compatibility issues.
As for editors, still primarily Vim, though there's a promising 6502 plugin for JetBrains things that might see me changing over, especially if I get around to submitting a patch for unintendeds and a couple of misconfigured addressing modes. |
| |
Starfox
Registered: Jul 2014
Posts: 31 |
Quote: In the past year or so, I've become a fan of cross assemblers under Linux because of their speed, but also because for any nontrivial project, I'm writing C code as some sort of tool or emulator instrumentation anyway.
In the beginning though, a Fastload cartridge and a notebook of paper all the way. :-)
I used to code on paper first too :) My grandma once saw me scribbling down some mc and thought it looked like I was communicating with aliens 😂
A good cartridge is very hand, indeed!
DeMOSic: I tried using 64TASS + notepad yesterday. No automation, just to test it out. I kind of like the barebones nature of such a setup, although I also use notepad++, sublime text normally together with kickass (which I only utilize 1% probably, lol).
Fungus: I find kickass's smart features too complex. I don't use macros, although they would probably make things easier. I have some speedcode for an effect that takes up 17kb, I wrote it all by hand in CBM PRG Studio. Switched to kickass, since CBM PRG Studio started having trouble with the length on the source code for that effect for some reason (I recall mentioning it to Arthur, who probably fixed it).
ChristopherJam: Interesting! I'm might check some of that out. I like, but am not a master of, Vim.
On another note: I often find the syntax highlighting in say, Sublime text or VSCode, to be rather incomplete. It will highlight some values in a color, but not others, some directivesm but not others. Sometimes I like just black text on a white background, and use notepad or something. What do you guys use for highlightning? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 - Next |
