A little late, but better late than never...
@pmc/Retro
That's really interesting to me guys - with all the people using AsmOne I've spoken to I thought I must be one of the only guys around still using Devpac.
Perhaps, in that case, use of Devpac is less a British thing like I suspected and it's more just that demo coders mainly use AsmOne. Probably for the very reason you gave matthey - expense - when most of the demo guys started coding stuff as teenagers in their bedrooms way back when they would've used whatever was available easiest and cheapest I suppose...
Yes, that makes sense.
Although I was one of those, who were able to purchase Devpac (1 and 2) I never did.
I sticked with Seka. The illegal copies of Devpac (1 and 2) I obtained at copy-parties were not comparable with Devpac3. Devpac3 was the assembler which I had to have after I illegally copied it! Because it was nowhere to purchase (not store had it) I wrote a letter to HiSoft in 1992. For 71 £ plus shipping cost I got it - and I have never regretted it!
@xeron
Hmm.. interesting. I thought nobody used DevPac any more. Certainly in the Amiga demoscene, Asm-One and Asm-Pro are pretty much "the standard".
As Frank (Phx) pointed out, who could afford Devpac3 purchased it.
If I am not mistaken, AsmOne / AsmPro are successors of K-Seka. Clones of K-Seka were used in the 80ths by any demo/intro coder because they were the fastest assemblers available (although all were illegal; K-Seka was the source and disassembled and enhanced in order to produce a clone). Where the duo 'ASSEM' (MetaComCo) and 'Alink' would require more than two minutes to build the executable, K-Seka (I used MasterSeka) required just three seconds. Unfortunately, not one K-Seka clone was conforming with the Motorola syntax, nor they did allow to generate linkable code (K-Seka's link command was just a bad joke). So source codes written and successfully assembled with 'ASSEM' didn't work under K-Seka and clones.
And the same happened with Devpac. Source codes created with Devpac3 couldn't be assembled by using AsmOne / AsmPro nor vice versa, at least not in those times when I tried them. Frankly, even AsmOne / AsmPro would have worked I wouldn't have stopped using Devpac3. I was only curious at these times.
@matthey
The newest vasm v1.4b (beta) is here...
Not entirely correctly anymore since Frank has since yesterday a new version available (1.4c).
As I already told, he is always very busy.
By the way. The official release of 'vbcc 0.9a' (yesterday) does not contain it.
@matthey
I got the -Fhunkexe working but I didn't use it for the ARexx scripts because I have amiga.lib look up function offsets. Vasm is more compatible with the linker.
Hmm, I never used the 'amiga.lib' in conjunction with any assembler. Because Devpac, which I used in the past, came with all '..._lib.i' files, I used them. And now that I am using 'vasm', I am still using these '...._lib.i' files for 'vasm'. No problems at all.
By the way, I didn't use the 'amiga.lib' for my projects because I don't like relocation data in my executable. If possible, the codes I built using assemblers were PC-relativ and often reentrant, too.
