<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/tass64/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/tass64/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/tass64/feature-requests/</id><updated>2026-05-23T17:02:34.082000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>#31 Option to always color diagnostics</title><link href="https://sourceforge.net/p/tass64/feature-requests/31/?limit=25#aec8" rel="alternate"/><published>2026-05-23T17:02:34.082000Z</published><updated>2026-05-23T17:02:34.082000Z</updated><author><name>Zane Avernathy</name><uri>https://sourceforge.net/u/zaneavernathy/</uri></author><id>https://sourceforge.neta38be82f164905da86dbc3dd027e80c6a65f2917</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Awesome, thank you!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#31 Option to always color diagnostics</title><link href="https://sourceforge.net/p/tass64/feature-requests/31/?limit=25#0105" rel="alternate"/><published>2026-05-23T06:59:23.767000Z</published><updated>2026-05-23T06:59:23.767000Z</updated><author><name>Soci/Singular</name><uri>https://sourceforge.net/u/soci/</uri></author><id>https://sourceforge.net26775d124188a28e7be332123a83da6d431d9866</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; pending&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>Option to always color diagnostics</title><link href="https://sourceforge.net/p/tass64/feature-requests/31/" rel="alternate"/><published>2026-05-19T06:40:59.161000Z</published><updated>2026-05-19T06:40:59.161000Z</updated><author><name>Zane Avernathy</name><uri>https://sourceforge.net/u/zaneavernathy/</uri></author><id>https://sourceforge.netf8dec6b501d5ed11ca1f247f130bb965735cc227</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hey there, Soci!&lt;/p&gt;
&lt;p&gt;64tass has automatic detection for when it should color its diagnostic output, but would it be possible to add an option to forcibly enable coloring?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;br/&gt;
~Zane&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Option to always color diagnostics</title><link href="https://sourceforge.net/p/tass64/feature-requests/31/" rel="alternate"/><published>2026-05-19T06:40:59.161000Z</published><updated>2026-05-19T06:40:59.161000Z</updated><author><name>Zane Avernathy</name><uri>https://sourceforge.net/u/zaneavernathy/</uri></author><id>https://sourceforge.nete72f82f9c3a6fb2d1e77481ddc3bea27dc67f0df</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 31 has been modified: Option to always color diagnostics&lt;br/&gt;
Edited By: Soci/Singular (soci)&lt;br/&gt;
Status updated: 'open' =&amp;gt; 'pending'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Allow long-branch option in source code (.option)</title><link href="https://sourceforge.net/p/tass64/feature-requests/30/" rel="alternate"/><published>2026-03-22T00:37:42.481000Z</published><updated>2026-03-22T00:37:42.481000Z</updated><author><name>Steve West</name><uri>https://sourceforge.net/u/seratosteve/</uri></author><id>https://sourceforge.neteb1eb199806a3884282caa0add03ac093b159426</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be useful to have the long branch option selectable inside the source code with the .option directive. There is an (undocumented) option auto_longbranch_as_jmp which does something else.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>o65 output type</title><link href="https://sourceforge.net/p/tass64/feature-requests/29/" rel="alternate"/><published>2026-02-09T01:12:55.424000Z</published><updated>2026-02-09T01:12:55.424000Z</updated><author><name>Adiee5</name><uri>https://sourceforge.net/u/adiee5/</uri></author><id>https://sourceforge.net368affe49457cbbe6df456c9ff1cf060148efd73</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Since 64tass already has many output types available, I think &lt;a class="" href="http://www.6502.org/users/andre/o65/fileformat.html" rel="nofollow"&gt;o65&lt;/a&gt; support would also fit there. This format is used by some unix-like operating systems and is also supported by the ca65 toolkit which can import these files into ca65 projects.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>feature request: Big endian datatype</title><link href="https://sourceforge.net/p/tass64/feature-requests/28/" rel="alternate"/><published>2025-09-04T15:34:27.667000Z</published><updated>2025-09-04T15:34:27.667000Z</updated><author><name>Jarkko Lehti</name><uri>https://sourceforge.net/u/gruelty/</uri></author><id>https://sourceforge.netaaf63a60b7b8d17cbe1f9baf4978ab6a07831ebc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello, I'm working on a reverse engineered c64 game source project and it has address tables in big endian format.&lt;br/&gt;
I have labels for the datasets, and table with the addresses there but its accessed in big endian way, and there doesn't seem to be a way to make the list just by&lt;/p&gt;
&lt;p&gt;.word label&lt;/p&gt;
&lt;p&gt;64tass manual mentions .text x "fce2" but that doesn't work with the labels.&lt;/p&gt;
&lt;p&gt;So, pretty please, could we have a ".bigword LABEL" or something else to present big endian format for the compiler?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#27 Syntax errors create hang</title><link href="https://sourceforge.net/p/tass64/feature-requests/27/?limit=25#1280/f380" rel="alternate"/><published>2025-05-18T18:12:26.303000Z</published><updated>2025-05-18T18:12:26.303000Z</updated><author><name>Soci/Singular</name><uri>https://sourceforge.net/u/soci/</uri></author><id>https://sourceforge.net83137cd1421c8e09b41e18b2a656381e554ca920</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello Fungus!&lt;/p&gt;
&lt;p&gt;Thanks for reminding! I've improved that part of the documentation a bit now:&lt;br/&gt;
&lt;a href="https://tass64.sourceforge.net/#repetitions" rel="nofollow"&gt;https://tass64.sourceforge.net/#repetitions&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#27 Syntax errors create hang</title><link href="https://sourceforge.net/p/tass64/feature-requests/27/?limit=25#1280" rel="alternate"/><published>2025-05-13T04:17:37.325000Z</published><updated>2025-05-13T04:17:37.325000Z</updated><author><name>Fungus </name><uri>https://sourceforge.net/u/fungusn0s/</uri></author><id>https://sourceforge.netdcd5672360682c0887fa8f1c89311708b41fd5c4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello Soci!&lt;/p&gt;
&lt;p&gt;OK that's nice, I will use that instead, thank you.&lt;/p&gt;
&lt;p&gt;I think some more/better examples in the manual would really help, I have no idea how to use a lot of them. Probably because I don't know C/C++ very well and it's assumed knowledge ;)&lt;/p&gt;
&lt;p&gt;Cheers.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#27 Syntax errors create hang</title><link href="https://sourceforge.net/p/tass64/feature-requests/27/?limit=25#8bdb" rel="alternate"/><published>2025-05-12T20:05:17.530000Z</published><updated>2025-05-12T20:05:17.530000Z</updated><author><name>Soci/Singular</name><uri>https://sourceforge.net/u/soci/</uri></author><id>https://sourceforge.net3bbff984ef8b6e0cfe7345a6b71f9e95a6cd0fd6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello Fungus!&lt;/p&gt;
&lt;p&gt;That's one of the common mistakes one can make when using this style of loop.&lt;/p&gt;
&lt;p&gt;First I thought that an error in the condition expression doesn't terminate the loop (it does), but it's a hard to spot typo and it's syntactically correct otherwise (the name is defined elsewhere).&lt;/p&gt;
&lt;p&gt;The 3 expressions are not restricted for certain variables or fixed syntax but are free form, so anything goes. Makes this style of loop powerful but also dangerous.&lt;/p&gt;
&lt;p&gt;Doing a loop finiteness check isn't feasible. Actually such mistakes were the reason for implementing proper Control+C interruption handling back then. Before that it was very difficult to figure out where such a loop formed.&lt;/p&gt;
&lt;p&gt;For simple loops as above I don't write this form any more. It's just too annoying to repeat 3 times the same variable name. Was even 4 before the compound expressions were added. Instead I'd write it in the iterator form:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="na"&gt;.for&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="no"&gt;sprites&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="no"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="no"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="no"&gt;sprite_start&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="no"&gt;sprite_end&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="no"&gt;$40&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;No variable name repetition, it's always bounded and not even slower as there's no repeated expression evaluation.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>