Which assembler?
16 messages in this thread
I started a book about ASM some days ago and I'm soon through the
theoretical part. I still don't know what assembler to buy.
I'd appreciate some recomendations.
–Quinten
Quinten –
Look in the LIBS for several assemblers that won't cost you more than
the CIS time. Also pick up a copy of BLINK. BLINK was originally a PD
linker that blew the original Amiga linker ALINK out of the water. It
should also be available.
– Nelson …
– via Whap!
Actually, BLINK 6.7 still is a Freely Redistributable linker. Also, given
that the hunks introducted by Blink are recognized by Commodore as standard
now, Alink won't even handle all the standard hunks.
John A. Toebes, VIII – via Whap!
Speaking of ALink… you know, CBM actually had the _nerve_ to send both
ALink and ATOM (remember that?) on the developer tool disks for 2.0…
Maybe they just wanted to test everyone's delete command.
<laughing>
Ben
On the other hand, if they didn't ship them, someone would be sure to ask
for them. 🙂 Let's hear it for the CBM developer CD-ROM, where they can
include *everything* without space considerations. As a lark, I suggest
they include all the source code to AmigaDOS and its utilities… the
worst thing that would happen is that the Amiga's hackers would find eleven
zillion ways to improve them, find bugs and bottlenecks… it's not like
Apple and IBM are going to steal the code. 🙂
It is actually not an issue of 'improving' or 'fixing bugs', but that
people would make many many changes in the code and prove to be a big
headache. We talked about this because the Software Distillery did the C:
commands. Making the source code available was much more of a headache
than you even want to deal with. At least now, all the bugs are consistent
:-).
John A. Toebes, VIII – via Whap!
I know… I said, "as a lark". they hand out the source to Unix, right?
Considering the large amount of software that was developed by third
parties that got folded into various release of AmigaDOS and developer tool
packs, it's not that outlandish that someone's improvements could be folded
into deeper bits of the OS.
Actually, they don't just 'hand out' the source to Unix. Last time I
checked, a source licence was somewhere in the 30K to 70K range. HPUX
seems to be a bit more.
John A. Toebes, VIII – via Whap!
Actually, before I left SAS, I was attempting to get things so that C=
could distribute Blink instead of Alink. It is quite funny to see. From
the developer standpoint, Alink does handle overlays while Blink 6.7 does
not. Later versions of Blink from SAS do handle overlays now.
John A. Toebes, VIII – via Whap!
That's what we use – the SAS Blink. ATOM….
I like the chip keyword, myself. :^)
Ben
You use ATOM? There is even a CHIP keyword on Blink to make it perform the
same functionality (well, almost the same functionaility).
John A. Toebes, VIII – via Whap!
Whoa! No – I don't use atom. :^) I was pointing out that they included it
on the developer disks, which I thought was pretty darn funny, given the
state of GOOD developement tools like SAS/c.
Ben
I'm pretty sure it was a cheap was to prevent the thousands of complaints
when people noticed they were missing. There's apparently a large group of
people who use PD C compilers, Pascal compilers, and assemblers who depend
on those utilities. (They also must reformat their old native developers
updates every time there's a new one available, but that's another story).
It's a lot easier to just include the utilities. Meanwhile, serious
developers use more up to date utilities 🙂
BTW, I still get complaints from people not being able to find the
clist.library. And that got dropped back in 1.1 days 🙂
andy
I'm not in the least surprised (clist.library requests)… although I am
amused. :^))
Ben
John –
Oops! You're right of course. Poor choice of words on my part. Sorry.
BLINK is copyright Software Distillery as I recall but is freely
distributable. But you'd know that better than I, no? 9-)
– Nelson …
– via Whap!
one and only one choice – Macro68. It handles EVERYTHING.