<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/acme-crossass/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/acme-crossass/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/acme-crossass/discussion/</id><updated>2026-10-26T07:16:48.548000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>v0.98 release to-do list?</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/4c23aa783a/?limit=25#13c7" rel="alternate"/><published>2026-10-26T07:16:48.548000Z</published><updated>2026-10-26T07:16:48.548000Z</updated><author><name>Piero Furiesi</name><uri>https://sourceforge.net/u/pf_spad/</uri></author><id>https://sourceforge.net75c02aca13b789cfadde12d33aef1852c1bf41d1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Marco,&lt;br/&gt;
that's a breaking but very useful feature. So I'm guessing that external references will be something as FILENAME.&lt;span&gt;[ZONENAME]&lt;/span&gt;.symbol, right?&lt;br/&gt;
Good job, that's useful to prevent namespace clashes.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>v0.98 release to-do list?</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/4c23aa783a/?limit=25#9822" rel="alternate"/><published>2026-10-25T23:32:38.707000Z</published><updated>2026-10-25T23:32:38.707000Z</updated><author><name>Marco Baye</name><uri>https://sourceforge.net/u/marcobaye/</uri></author><id>https://sourceforge.net297e0c5e37888168087c0f3155edab1850e9a735</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks, but the main hurdle is that I have the update the documentation for the new features, especially for the three incompatibilities (paths are now relative to the file they are in, forward referencing a symbol no longer forces it to 16 bits, zone titles are no longer meaningless).&lt;br/&gt;
So that's not really something the community can help me with.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>BRK is a two byte instruction</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/af42b99a29/?limit=25#94fb" rel="alternate"/><published>2026-08-15T09:08:57.844000Z</published><updated>2026-08-15T09:08:57.844000Z</updated><author><name>Matt Sage</name><uri>https://sourceforge.net/u/mattbsage/</uri></author><id>https://sourceforge.netba10d1e3755cea3153d467e739650a3c0d1ba394</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Bula!&lt;/p&gt;
&lt;p&gt;I've been working with my W65C02SXB SBC, implementing a terminal/debugger.  I've successfully built code with acme, deployed it and run it.&lt;/p&gt;
&lt;p&gt;Most recently, I've been experimenting with breakpoints - when the code hits a BRK instruction, the program hands over to the debugger which is accessed via the IRQ vector.&lt;/p&gt;
&lt;p&gt;The problem is that the code was not resuming.&lt;/p&gt;
&lt;p&gt;I've worked out that the PC is being advanced two bytes (effective after the RTI), which means the code is not correctly aligned because acme-assembler only uses one byte for the BRK instruction.&lt;/p&gt;
&lt;p&gt;I have confirmed that BRK is indeed, a two byte instruction - taking an IMMEDIATE byte as an operand.  Note that the addressing mode is still classified as "stack" and the operand is ignored by the MPU but can be accessed by retrieving the return vector from the stack, loading the operand and replacing the return vector.  Having distinct software interrupts is a useful feature of the processor (especially for debugging - not so much for regular programming as the overhead of pushing the PC and P flag to the stack is costly) and I haven't yet found any cross-assembler that implements the BRK mnemonic correctly.&lt;/p&gt;
&lt;p&gt;Confirmation for the original NMOS 6502, the WDC 65C02 and the WDC 65C816 versions can be found in the WDC 65C816 datasheet.  See Section 7.2 on page 53 below.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.westerndesigncenter.com/wdc/documentation/w65c816s.pdf" rel="nofollow"&gt;https://www.westerndesigncenter.com/wdc/documentation/w65c816s.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;NMOS 6510 "confirmation" is in the VICE source, line 1002:&lt;br/&gt;
&lt;a href="https://sourceforge.net/p/vice-emu/code/HEAD/tree/trunk/vice/src/6510core.c#l1002"&gt;https://sourceforge.net/p/vice-emu/code/HEAD/tree/trunk/vice/src/6510core.c#l1002&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Although the simplest workaround is to always break twice,&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;brk
brk
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;and a "better" workaround can implemented with a macro,&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="sx"&gt;!macro brk .byte {&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="n"&gt;brk&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;!&lt;span class="n"&gt;byte&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;byte&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;it would be nice if the assembler could support the BRK instruction as designed.  One issue is that with the macro, is if a word is passed, the generated error occurs at the macro definition, not at the bad call.&lt;/p&gt;
&lt;p&gt;I doubt this change will cause any backward compatibility issues (unless some existing code was written specifically to work around the improper assembly) because I'm guessing most folks use BRK as a means to terminate execution, if at all.&lt;/p&gt;
&lt;p&gt;For maintaining source compatibility, I imagine that a bare BRK could be handled by issuing a warning and assembling a "double" BRK, under-the-hood style.  I'm not sure why anyone would want to force the bare BRK unless they have implemented their emulators incorrectly. :-)&lt;/p&gt;
&lt;p&gt;I'm interested to know your thoughts...  I would have submitted this as a ticket but I don't have permission.&lt;/p&gt;
&lt;p&gt;Many thanks.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>(no subject)</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/314c87d7c1/?limit=25#bb9b" rel="alternate"/><published>2026-04-29T09:15:13.578000Z</published><updated>2026-04-29T09:15:13.578000Z</updated><author><name>Marco Baye</name><uri>https://sourceforge.net/u/marcobaye/</uri></author><id>https://sourceforge.net42bea25d7296cc4bb8a20fada1a07d9dfc511b96</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The reason for the "number does not fit" error is this:&lt;br/&gt;
"!$c0" evaluates to 0xffffff3f (on a 32-bit system) or 0xffffffffffffff3f (on a 64-bit system).&lt;br/&gt;
So in a case like this, you could use&lt;br/&gt;
255 - $c0&lt;br/&gt;
or&lt;br/&gt;
$c0 XOR $ff&lt;br/&gt;
instead to flip all bits.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>(no subject)</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/314c87d7c1/?limit=25#6ac4" rel="alternate"/><published>2026-04-21T15:38:00.096000Z</published><updated>2026-04-21T15:38:00.096000Z</updated><author><name>Jake Hamby</name><uri>https://sourceforge.net/u/jakehamby/</uri></author><id>https://sourceforge.net7081e3dca7246b672f7798c6a7858a84e3e5b696</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The following line doesn't work for me (including with the latest ACME source code):&lt;/p&gt;
&lt;p&gt;and #!$C0&lt;/p&gt;
&lt;p&gt;Error - File basic3.asm, line 1793 (Zone &amp;lt;untitled&amp;gt;): Number does not fit in 8 bits.&amp;lt;/untitled&amp;gt;&lt;/p&gt;
&lt;p&gt;I worked around it by changing the line to "and #$5F" but it's strange. I tried using "and+1" but that didn't help. Everything else looks great!&lt;/p&gt;
&lt;p&gt;-Jake&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Arbitrary number of arguments for macro</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/0a04353f0b/?limit=250#0dfa" rel="alternate"/><published>2024-06-17T12:54:36.176000Z</published><updated>2024-06-17T12:54:36.176000Z</updated><author><name>Jimmy Dansbo</name><uri>https://sourceforge.net/u/xpinex/</uri></author><id>https://sourceforge.netadaf6c006a31c47d7bf4d6530e9a201c07abac19</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks for those very clear examples, may I suggest they get added to the documentation?&lt;br/&gt;
Will this also work with an argument list passed by reference, ie. ~@listarg ?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Arbitrary number of arguments for macro</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/0a04353f0b/?limit=25#9352" rel="alternate"/><published>2024-06-17T11:31:48.082000Z</published><updated>2024-06-17T11:31:48.082000Z</updated><author><name>Marco Baye</name><uri>https://sourceforge.net/u/marcobaye/</uri></author><id>https://sourceforge.net13b318b5f47a3070cbb6188b96712e63db8a350a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This works since the 0.97 release:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="sx"&gt;!macro example1 @listarg {&lt;/span&gt;
&lt;span class="w"&gt;            &lt;/span&gt;!&lt;span class="k"&gt;for&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(@&lt;/span&gt;&lt;span class="n"&gt;listarg&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
&lt;span class="w"&gt;                    &lt;/span&gt;!&lt;span class="n"&gt;warn&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="n"&gt;listarg&lt;/span&gt;&lt;span class="p"&gt;[@&lt;/span&gt;&lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="w"&gt;            &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="n"&gt;example1&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;&amp;lt;-&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;macro&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;will&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;iterate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;over&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;list&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;items&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="n"&gt;example1&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"string"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;&amp;lt;-&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;macro&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;will&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;iterate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;over&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;characters&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;If you compile from source, you can also use this newer, simpler syntax, which is not in the docs yet:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;macro&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;example2&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;listarg&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
&lt;span class="w"&gt;            &lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;for&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;listarg&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
&lt;span class="w"&gt;                    &lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;warn&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;item&lt;/span&gt;
&lt;span class="w"&gt;            &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="n"&gt;example2&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="m"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="m"&gt;5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="m"&gt;7&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;&amp;lt;-&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;macro&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;will&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;iterate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;over&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;list&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;items&lt;/span&gt;
&lt;span class="w"&gt;    &lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="n"&gt;example2&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s"&gt;"string"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;&amp;lt;-&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;macro&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;will&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;iterate&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;over&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;characters&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;The "!for X in Y" syntax will be officially introduced in the next release of ACME, but it has been in the source for quite some time now.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Arbitrary number of arguments for macro</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/0a04353f0b/?limit=250#9fe7" rel="alternate"/><published>2024-06-17T06:10:25.323000Z</published><updated>2024-06-17T06:10:25.323000Z</updated><author><name>Jimmy Dansbo</name><uri>https://sourceforge.net/u/xpinex/</uri></author><id>https://sourceforge.net913b89d699ec2640fdb22dd46275fef3f0c226f9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I found this in the documentation for macros:&lt;/p&gt;
&lt;p&gt;"Since release 0.97, lists are supported. This is useful for macros if&lt;br/&gt;
you want an arbitrary number of arguments: Just define the macro with&lt;br/&gt;
a single argument, then pass a list and have the macro iterate over&lt;br/&gt;
its contents."&lt;/p&gt;
&lt;p&gt;Could someone provide an example on how to pass a  list to a macro and then have that macro iterate over the list?&lt;br/&gt;
Thanks.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Instructions?</title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/1c5da2872a/?limit=25#f2fa" rel="alternate"/><published>2024-02-03T12:27:33.363000Z</published><updated>2024-02-03T12:27:33.363000Z</updated><author><name>Jan Sefcik</name><uri>https://sourceforge.net/u/jjcale/</uri></author><id>https://sourceforge.netd4ab2beb51406f94e8c4a620ecf53517cee6fcef</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Quick reference, pseudo opcodes, examples:&lt;br/&gt;
&lt;a href="https://github.com/martinpiper/ACME/blob/master/docs/QuickRef.txt" rel="nofollow"&gt;https://github.com/martinpiper/ACME/blob/master/docs/QuickRef.txt&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>How can I bind the ACME_Lib folder? </title><link href="https://sourceforge.net/p/acme-crossass/discussion/general/thread/a5d918afcd/?limit=25#c430" rel="alternate"/><published>2023-09-12T09:04:53.374000Z</published><updated>2023-09-12T09:04:53.374000Z</updated><author><name>Gonzales</name><uri>https://sourceforge.net/u/gonzales555/</uri></author><id>https://sourceforge.netc3b28259c99d1f6afd59dec9d9319ae80f95a619</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;So i have found the solution by myself: if anyone has the same problem:&lt;br/&gt;
before you use acme to build you have to declare this environment variable with "export ACME=./ACME_Lib/"&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>