document a30ac2c

better late than never i guess

Author: trillllian

docs/changelog/index.html

@@ -111,6 +111,7 @@ <h3>New features:</h3>
 			<li>Variadic macro support (p4plus2)</li>
 			<li>Support for global labels (p4plus2)</li>
 			<li>Errors about crossing banks have been improved, now they print the exact line where the bank border was crossed instead of saying it was "somewhere before this point". (randomdude999)</li>
+			<li>Add <code>fill align</code> and <code>skip align</code> (randomdude999)</li>
 		</ul>
 
 		<h3>Bug fixes:</h3>

docs/manual/index.html

@@ -1748,13 +1748,21 @@ <h4 id="base">base</h4>
 base off
 	rtl</code></pre>
 		<h4 id="skip">skip</h4>
-		<pre><code class="65c816_asar">skip {num_bytes}</code></pre>
-		The skip command moves the pc by <code>num_bytes</code> bytes. By specifying a negative value, the pc can be moved backwards.
+		<pre><code class="65c816_asar">skip {num_bytes}
+skip align {alignment} [offset {offset}]</code></pre>
+		The skip command moves the pc by <code>num_bytes</code> bytes. By specifying a negative value, the pc can be moved backwards. When <code>alignment</code> is given, skips to the next multiple of <code>alignment</code>, plus <code>offset</code> if it is specified. Note that the alignment must be a power of 2, if specified. Offset can also be negative, in that case it's treated exactly like <code>alignment+offset</code>. The seeked-to position will always be after the current SNES position, but it might be before the next multiple of <code>alignment</code>: see the last example.
 		<pre><code class="65c816_asar">org $008000
 skip 5
 ; pc is now at $008005
 skip -1
-; pc is now at $008004</code></pre>
+; pc is now at $008004
+skip align 16
+; pc is now at $008010
+skip align 16 offset 5
+; pc is now at $008015
+skip align $20 offset $17
+; pc is now at $008017
+</code></pre>
 		<h4 id="warnpc">warnpc</h4>
 		<pre><code class="65c816_asar">warnpc {snes_address}</code></pre>
 		The warnpc command checks if the current pc is <code>&gt; snes_address</code>. If that's the case, it throws an error. This is useful for detecting overflow errors.
@@ -2945,11 +2953,16 @@ <h4 id="tables">Tables</h4>
 db "something ""cool"""</code></pre>
 		<h4 id="fill">fillbyte/fill</h4>
 		<pre><code class="65c816_asar">fillbyte {byte}</code></pre>
-		<pre><code class="65c816_asar">fill {num}</code></pre>
-		The fillbyte and fill commands let you write a specific byte value to the ROM multiple times. The <code>byte</code> parameter of fillbyte specifies which value to write, wheres fill writes that value to the output ROM <code>num</code> times.
+		<pre><code class="65c816_asar">fill {num}
+fill align {alignment} [offset {offset}]</code></pre>
+		The fillbyte and fill commands let you write a specific byte value to the ROM multiple times. The <code>byte</code> parameter of fillbyte specifies which value to write, wheres fill writes that value to the output ROM <code>num</code> times. If <code>alignment</code> is specified, the value will be written repeatedly until the SNES address has the specified alignment, similar to <code>skip align</code>.
 		<pre><code class="65c816_asar">fillbyte $FF
 ; This writes $FF $FF $FF $FF $FF $FF $FF $FF
-fill 8</code></pre>
+fill 8
+org $008005
+; this writes $FF until SNES address $00800A (=$8008 + 2)
+fill align 8 offset 2
+</code></pre>
 		It's also possible to write 16-bit, 24-bit or 32-bit values with the fill command by using <code>fillword</code>, <code>filllong</code> or <code>filldword</code> instead of fillbyte. Note that the <code>num</code> parameter of fill still specifies the number of bytes to write in those cases. Values might get truncated as needed to exactly reach the specified number of bytes to write.
 		<h4 id="pad">padbyte/pad</h4>
 		<pre><code class="65c816_asar">padbyte {byte}</code></pre>