AsmPro 1.19

[kamelito]

Did you also missed it?

http://aminet.net/package/dev/asm/ASMPro1.19

Update for the ASM-Pro package, includes latest executable. Now in a
Y2K compliant .lha file .
Some of the older versions use ENVARC:Asm-Pro_beta.Pref instead of
ENVARC:Asm-Pro.Pref. If your preferences don't look OK, please ensure
that you have the correct (not beta) .Pref file.

This release fixes a number of KS2.x, 68000/010, and FPU compatibility
issues, as well as a large number of other issues (over 60 bugfixes in
total, see the history file for details). You can run it on KS2.04+
and 68000 based systems again.
Code has been cleaned up and optimized (over 2600 micro optimizations,
and a number of subroutines rewritten), resulting in 15KB reduction of
the executable size and a smaller memory footprint overall.

Additions (detailed description available in the history file):
1. WX command to enable short code and data hunks (code+bss, data+boss)
2. ADDBP directive to add a breakpoint from the source code
3. Command line history jump by 10 lines, don't store repeated lines
4. Macro symbol parameter \<symbol> and \<$symbol> (vasm style)
5. Assembly elapsed time

IF YOU FIND ANY ADDITIONAL KS2.X OR 68000/010 ISSUES, OR IF SOMETHING
DOES NOT WORK PROPERLY, COMPARED TO v1.18 (read: if I messed up :P),
PLEASE LET ME KNOW. I'll do my best to fix them.

[veper]

Wow, now this is a nice xmas surprise

[TCD]

Originally Posted by kamelito

Did you also missed it?

Nope: http://eab.abime.net/showthread.php?...51#post1584951

Better to have a dedicated thread about it though

[a/b]

Originally Posted by TCD

Nope: http://eab.abime.net/showthread.php?...51#post1584951

Better to have a dedicated thread about it though

Interesting concept.

[StingRay]

I take it, ASM-Pro 1.19 is now closed source again? Former versions were open source and in my opinion, it should stay like that. Thanks for the update though, may try it once I decide to switch from 1.16d.

[kamelito]

He may release the source if someone ask for it.

[paraj]

Nice, I was on 1.17 since 1.18 seemed unstable in some situations. Only took it for a quick spin, but one thing I noticed is that even after nuking preferences the "Read source" dialog defaults to a pattern of "#?#?.Pref" (reqtools.library version 38.1436).

Otherwise good job a/b

[StingRay]

Originally Posted by kamelito

He may release the source if someone ask for it.

ASM-Pro has been open source since 2000, seeing that one now, more than 20 years later, has to ask for the source just doesn't feel right to me.

[kamelito]

I agree with you it has been like that for some open sourced game ports too…

[a/b]

Source code will absolutely be released, 1.19 wouldn't exist without that. Why not right now?
1. I'm expecting new bugs, too many changes and I want to take care of those first.
2. I'm not done yet, I still have to iron out a few things.
3. Right now source code = old source code with a bunch of stuff commented out + over 100kb of my changes, with every single little change "marked" so I know what/why/how, and I have to clean that up first.

[StingRay]

In that case, I have nothing to complain about. Thanks for updating ASM-Pro, I know how much "fun" it is to work with the mess that is ASM-Pro's source code.

[a/b]

Originally Posted by paraj

Nice, I was on 1.17 since 1.18 seemed unstable in some situations. Only took it for a quick spin, but one thing I noticed is that even after nuking preferences the "Read source" dialog defaults to a pattern of "#?#?.Pref" (reqtools.library version 38.1436).

Otherwise good job a/b

Yeah, that's a know bug, already reported yesterday: if you have Source .ASM enabled in the general preferences (I never did ><), it will mess up the pattern. Lovely implicit dependencies straight from resource.
I'll upload 1.19a in the zone.

[kamelito]

Thanks

[StingRay]

I finally got around to testing 1.19a, Set Start/End in the hex dump doesn't appear to work anymore. "Set Start" doesn't seem to do anything at all, "Set End" apparently performs "Set Start". As I use this functionality quite often, this should be fixed.

If something is unclear or you need more info, just let me know. First impression of 1.19a is that I may finally switch from 1.16d once the aforementioned problem will be fixed.

[a/b]

Hmm... I did test that because of a change (if start or end address was a 0 you couldn't save, now it uses a is-set flag for both) and it worked fine.
I'm trying it now (1.19 + 1.19a)... amiga-, to set start address, amiga-. to set end address, amiga-w to save. Also tried directly via the menus, all worked fine for me.
When you start both start and end should be empty (in the status bar), and once you set them they are ready to go every time.
Tried with end < start (it will swap them), worked fine. File lengths checked out, contents is also ok.

Is this borked for you right from the start, or after a while, ...?

[StingRay]

Appears to be broken right from the start. Here's how I do it:

1. Read any source
2. h.l"Label_in_Source", e.g. if there's a label called "Test" in the source, it would be h.lTest
3. Select "Set Start" from the "Monitor" menu, the "Start" address in the status bar will not be updated at all, it stays empty.
4. Select "Set End" from the "Monitor" menu, the "Start" address in the status bar will be set to the selected end address.

[a/b]

You're onto something. I had the wrong 1.19a. Just extracted it again from the lha, it's not working (it's fine in 1.19).
OK, brb...

[a/b]

That was a nice sausage fingers ctrl+T, I swapped 2 lines by accident and borked the cmp/beq for start/end address. 1.19b is in the zone.
I've also included the latest internal 1.19 for the brave souls out there ;P. So you are not completely in the dark, it's a couple of crash fixes for 1.18 (no diskfont lib, apollo dbcc on 000/010 with specific conditions) and a bunch of asm/disasm fixes for borked/unimplemented exotics like callm, cmp2, chk2, cinv/cpush, moves, pmove, fmove(m) as I'm making my way through the disassembler code...

[kamelito]

There is a disassembler library on Aminet maybe you could use it instead?

[StingRay]

Originally Posted by a/b

That was a nice sausage fingers ctrl+T, I swapped 2 lines by accident and borked the cmp/beq for start/end address. 1.19b is in the zone.

Interesting bug. Thanks for the quick fix, it's working as expected now.