Batch Conversion Limitations - Revision history

Parricc at 19:51, 21 April 2026

2026-04-21T19:51:34Z

← Older revision		Revision as of 12:51, 21 April 2026
Line 14:		Line 14:
	</pre>		</pre>

	Instead, anything that is nested should have spacing to indicate the level of nesting. ~~Indentation~~ on closing parentheses is especially important as that is how the converter determines the boundary.		Instead, anything that is nested should have spacing to indicate the level of nesting. Correct indentation on closing parentheses is especially important as that is how the converter determines the boundary.

	Example that successfully converts:		Example that successfully converts:
Line 33:		Line 33:
	set conf=".\emulators\dosbox\Staging_noline_sl.conf"		set conf=".\emulators\dosbox\Staging_noline_sl.conf"
	goto preinstall)))		goto preinstall)))
	</pre>		</pre>When all of the closing parenthesis are together, the converter splits them apart and converts each one as appropriate.

	=== Labels must never be placed inside of loops or conditions. ===		=== Labels must never be placed inside of loops or conditions. ===

Parricc at 19:48, 21 April 2026

2026-04-21T19:48:50Z

← Older revision		Revision as of 12:48, 21 April 2026
Line 14:		Line 14:
	</pre>		</pre>

	Instead, anything that is nested should have spacing to indicate the level of nesting. ~~The~~ closing parentheses ~~are~~ especially important.		Instead, anything that is nested should have spacing to indicate the level of nesting. Indentation on closing parentheses is especially important as that is how the converter determines the boundary.

	Example that successfully converts:		Example that successfully converts:

Parricc at 19:44, 21 April 2026

2026-04-21T19:44:45Z

← Older revision		Revision as of 12:44, 21 April 2026
Line 1:		Line 1:
	For batch files to successfully convert into bash files for Linux and MacOS, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.		For batch files to successfully convert into bash files for Linux and MacOS, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.

	=== Indenting nested if statements and for loops is necessary. ===		=== Indenting multi-line nested if statements and for loops is necessary. ===
	With the limitations of tooling, nested statements that written without indentation will fail to convert.		With the limitations of tooling, nested statements that written without indentation will fail to convert.

Line 24:		Line 24:
	)		)
	)		)
			</pre>

			Something like this is also okay:
			<pre style="color: blue;">
			if %nsl%==On (
			if %PPmode%==Off (
			if %filter%==On (
			set conf=".\emulators\dosbox\Staging_noline_sl.conf"
			goto preinstall)))
	</pre>		</pre>

Parricc at 18:54, 21 April 2026

2026-04-21T18:54:21Z

← Older revision		Revision as of 11:54, 21 April 2026
Line 5:		Line 5:

	Example that fails to convert:		Example that fails to convert:
	<pre>		<pre style="color: red;">
	if [...] (		if [...] (
	some command		some command
Line 17:		Line 17:

	Example that successfully converts:		Example that successfully converts:
	<pre>		<pre style="color: blue;">
	if [...] (		if [...] (
	some command		some command
Line 30:		Line 30:

	Example that fails to convert:		Example that fails to convert:
	<pre>		<pre style="color: red;">
	if exist file2.txt goto mylabel		if exist file2.txt goto mylabel
	if exist .\mydir\file1.txt (		if exist .\mydir\file1.txt (
Line 40:		Line 40:

	Example that successfully converts:		Example that successfully converts:
	<pre>		<pre style="color: blue;">
	if exist file2.txt goto mylabel		if exist file2.txt goto mylabel
	if exist .\mydir\file1.txt (		if exist .\mydir\file1.txt (

Parricc at 18:51, 21 April 2026

2026-04-21T18:51:57Z

← Older revision		Revision as of 11:51, 21 April 2026
Line 2:		Line 2:

	=== Indenting nested if statements and for loops is necessary. ===		=== Indenting nested if statements and for loops is necessary. ===
	With the limitations of tooling, nested statements that written without indentation~~, such as the below example,~~ will fail to convert:		With the limitations of tooling, nested statements that written without indentation will fail to convert.

			Example that fails to convert:
	<pre>		<pre>
	if [...] (		if [...] (
Line 14:		Line 16:
	Instead, anything that is nested should have spacing to indicate the level of nesting. The closing parentheses are especially important.		Instead, anything that is nested should have spacing to indicate the level of nesting. The closing parentheses are especially important.

	Example that ~~correctly~~ converts:		Example that successfully converts:
	<pre>		<pre>
	if [...] (		if [...] (
Line 26:		Line 28:
	=== Labels must never be placed inside of loops or conditions. ===		=== Labels must never be placed inside of loops or conditions. ===
	The converted goto function has been designed to work through stack frames for Linux and MacOS. For this reason, a label must never be placed inside of a loop or condition. Such code will fail to convert.		The converted goto function has been designed to work through stack frames for Linux and MacOS. For this reason, a label must never be placed inside of a loop or condition. Such code will fail to convert.
	Example:
			Example that fails to convert:
	<pre>		<pre>
	if exist file2.txt goto mylabel		if exist file2.txt goto mylabel

Parricc: /* Indenting nested if statements and for loops is necessary. */

2026-04-21T18:47:40Z

Indenting nested if statements and for loops is necessary.

@@ Line 1: / Line 1: @@
-For batch files to successfully convert into bash files for Linux, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.
+For batch files to successfully convert into bash files for Linux and MacOS, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.
 === Indenting nested if statements and for loops is necessary. ===
-=== Labels must never be placed inside of loops. ===
+Instead, anything that is nested should have spacing to indicate the level of nesting. The closing parentheses are especially important.

Parricc at 18:15, 21 April 2026

2026-04-21T18:15:55Z

← Older revision		Revision as of 11:15, 21 April 2026
Line 1:		Line 1:
	For batch files to successfully convert into bash files for Linux, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.		For batch files to successfully convert into bash files for Linux, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.

	~~Indentation of~~ nested if statements and loops is necessary.		=== Indenting nested if statements and for loops is necessary. ===

			=== Labels must never be placed inside of loops. ===
	Labels must never be placed inside of loops.

Parricc: describes conversion limitations that must be considered when editing batch files

2026-04-21T18:13:55Z

describes conversion limitations that must be considered when editing batch files

New page

For batch files to successfully convert into bash files for Linux, there are some limitations for how they can be written. This page is to ensure that team members writing batch files are aware of some of those limitations.

Indentation of nested if statements and loops is necessary.

Labels must never be placed inside of loops.