| |
ChristopherJam
Registered: Aug 2004
Posts: 1380 |
Assembler preferences.
Two questions:
- what's everyone using these days?
- on large productions, do groups tend to enforce a single assembler for the entire project, or is the code base a bit heterogenous?
I'd like to keep this discussion purely focussed on assemblers; please leave code generators, loader toolchains etc for that other thread.
(as for me, I'm still using xa65 for most projects) |
|
... 204 posts hidden. Click here to view all posts....
|
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Mr Sid: I checked out K2Asm and saw you have bracket scopes for avoiding clash of labels. Nice, I thought KickAssembler was the only one to support this style :-) (And that I was one of the only ones to used it, since people have gotten use to referencing back and forth with multilabels) |
| |
Axis/Oxyron
Registered: Apr 2007
Posts: 91 |
@AlexC: I guess 90% of the people will awnser "I someday started cross-dev with this asm and now I´m used to it". As a coder you also build a kind of a framework of libraries and code-snippets you always re-use. And no one feels like porting all this stuff to a different asm. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 500 |
Quote: Useful addition to current discussion would be explanation why particular assembler is being used IMHO.
If it is just about typing in assembler it doesn't matter much which assembler you use, but there are things that can annoy with other assemblers. Therefore ACME is capable of:
- it handles labels without that additional colon, i hate that extra typing work
- it supports short labels like +/- (even though you can fuck yourself really hard if you overlook one of those small labels and then branch too far), as well as *+x as we know them from old tass times, right?
- macros with references
- support of local labels, be it per macro or zone
- supports all illegal menomonics, so noa ugly macro/!byte workarounds
Also as Peiselulli already stated, ACME is still actively maintained and it is fast.
Also, i don't see any problem at all to integrate a multitude of different assemblers with scripts/Makefiles as long as they are called via some commandline. No need to fall back into stoneage and receiving binary blobs. There's repositories we can use in a group and you can still hand out readymade .d64 images to those who are unable to build the whole project. At least all coders can build it (and even more), that is sufficient. |
| |
Fungus
Registered: Sep 2002
Posts: 624 |
64tass is also actively maintained and fast. soci has been active in this thread? |
| |
CSixx
Registered: Jan 2013
Posts: 12 |
Kickass, does what I need and is in java so I use the same executable everywhere (win, linux, etc..) |
| |
soci
Registered: Sep 2003
Posts: 474 |
Fungus: Yes, I've mentioned that I'm using it a few posts ago. Btw, sometime soon there should be another snapshot with the fixes/corrections done since 1.51.992.
I could try push it as the next best thing since sliced bread, but there's no point. Especially that I know which areas could be improved and lacking currently. But for the stuff I use it surely beats the others ;) Or else I would have given up on it long ago (almost happened around 1.4x). |
| |
algorithm
Registered: May 2002
Posts: 702 |
Quote: If it is just about typing in assembler it doesn't matter much which assembler you use, but there are things that can annoy with other assemblers. Therefore ACME is capable of:
- it handles labels without that additional colon, i hate that extra typing work
- it supports short labels like +/- (even though you can fuck yourself really hard if you overlook one of those small labels and then branch too far), as well as *+x as we know them from old tass times, right?
- macros with references
- support of local labels, be it per macro or zone
- supports all illegal menomonics, so noa ugly macro/!byte workarounds
Also as Peiselulli already stated, ACME is still actively maintained and it is fast.
Also, i don't see any problem at all to integrate a multitude of different assemblers with scripts/Makefiles as long as they are called via some commandline. No need to fall back into stoneage and receiving binary blobs. There's repositories we can use in a group and you can still hand out readymade .d64 images to those who are unable to build the whole project. At least all coders can build it (and even more), that is sufficient.
+the useful !pseudopc feature that is rather useful for code transferred and running in other area's (e.g zeropage) |
| |
Oswald
Registered: Apr 2002
Posts: 5023 |
64tass can do all of that. and I bet all the others. anyways I find myself most of the time using just very basic assembler features.
the most complex thing is usually a for loop to calculate a table of a number multiplied. |
| |
enthusi
Registered: May 2004
Posts: 675 |
I switched to xa since at the time, acme had no defines. it does now. xa also has .( and .) for local label space. It knows ascii, petscii and petscreen. also *= sets the pc. just that. No automated filling and shit *g*. |
| |
Fungus
Registered: Sep 2002
Posts: 624 |
soci: kewl, look forward to the update. Did you add a pseudopc function that can also return the length of the code somehow? Useful for disk stuff and relocating routines at runtime. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | ... | 22 - Next |
