| |
Mac Bacon
Registered: Feb 2016 Posts: 6 |
New ACME release
Hi!
ACME release 0.97 is here.
Now with string symbols (finally!), lists, backslash escaping, "unpseudopc"-operator, MEGA65 support, !while, else if, and a CLI switch to mimic older versions. The switch is needed because some of the changes introduce a slight incompatibility. Please make sure to read "docs/Changes.txt" and "docs/Upgrade.txt".
The project can be found at http://sourceforge.net/projects/acme-crossass/
There's a zip archive for windows users; linuxers should just download the code and use "make; make userinstall" to build and install their own binary.
Have fun! |
|
| |
Frantic
Registered: Mar 2003 Posts: 1625 |
Just downloaded the mac binary which was also there. It seems to work fine. A feature request would be to add a keyword of some kind that will include a breakpoint in the output of vicelabels, so you can just type "!vicebreak" in the source, and have the breakpoint(s) added to that file. |
| |
Krill
Registered: Apr 2002 Posts: 2801 |
Workaround: .byte 2 =) |
| |
oziphantom
Registered: Oct 2014 Posts: 477 |
yeah but that changes the code layout which can be bad. I have it in 64TASS, I made a VBS script that did tass -> Vice as I did this before 64tass actually added native vice output. I just filter all the labels with BREAK in them and convert them to break statements. WATCH etc
It would be nice to have build in, but a post pass is not that much work to do on the labels file. |
| |
Krill
Registered: Apr 2002 Posts: 2801 |
Quoting oziphantomyeah but that changes the code layout which can be bad. Hence workaround. Also doesn't work with emulated CMOS 6502 variants. |
| |
Martin Piper
Registered: Nov 2007 Posts: 621 |
Over the past couple of years I added extras such as:
* Library include paths
* Full program database debug, with section information
* Vice remote debugger with mixed source and assembly (uses the above debug) (Oziphantom also added a bunch of visualisation functionality)
* Much improved forward reference resolution, for situations where code size can change later offsets by variable amounts
* Microsoft Visual Studio format warnings and errors, to enable the "go to next error" functionality
* Extra binary import options, to skip bytes
Full commit history is: https://github.com/martinpiper/ACME/commits/master |
| |
Mac Bacon
Registered: Feb 2016 Posts: 6 |
Quote: Just downloaded the mac binary which was also there. It seems to work fine. A feature request would be to add a keyword of some kind that will include a breakpoint in the output of vicelabels, so you can just type "!vicebreak" in the source, and have the breakpoint(s) added to that file.
Sounds reasonable, I'm working on it. How about this:
!watch [comma-separated flags] ; add watch point/break point
!trace [comma-separated flags] ; add trace point
flags are load/store/exec. if none are given, all three are used. |
| |
Mac Bacon
Registered: Feb 2016 Posts: 6 |
Quoting Martin PiperOver the past couple of years I added extras
That's great, but please mark your fork clearly as a fork.
After a quick glance at your Changelog.txt file, you seem to haven taken my release 0.93 and built your work on that without merging any of my later changes (or submitting yours).
If you had called your releases "0.93mp", "0.93mp2", "0.93mp3" etc., there would be no confusion. |
| |
Martin Piper
Registered: Nov 2007 Posts: 621 |
Quote: Quoting Martin PiperOver the past couple of years I added extras
That's great, but please mark your fork clearly as a fork.
After a quick glance at your Changelog.txt file, you seem to haven taken my release 0.93 and built your work on that without merging any of my later changes (or submitting yours).
If you had called your releases "0.93mp", "0.93mp2", "0.93mp3" etc., there would be no confusion.
Done
https://github.com/martinpiper/ACME/commit/867dba138bda41e24012.. |