String Parsing Optimization - Revision history

Songbird at 20:17, 26 August 2020

2020-08-26T20:17:47Z

Songbird: /* [random x to y] */

2017-08-15T18:12:25Z

[random x to y]

← Older revision		Revision as of 18:12, 15 August 2017
Line 149:		Line 149:

	A complex [one of][or][at random] statement converted into a [random x to y] statement.		A complex [one of][or][at random] statement converted into a [random x to y] statement.

	~~Note that [with odds: ] has superseded much [case ]-statement with [random x to y] optimization wizardry.~~

	<br>		<br>

Songbird at 18:08, 15 August 2017

2017-08-15T18:08:44Z

← Older revision		Revision as of 18:08, 15 August 2017
Line 159:		Line 159:


	This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely ~~Songb~~'s. Please only modify with either A) explicit permission to do so, or B) a fix for known factual inaccuracy / grammar errors.		This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Song's. Please only modify with either A) explicit permission to do so, or B) a fix for known factual inaccuracy / grammar errors.

	[[Category:Guides]][[Category:Code]]		[[Category:Guides]][[Category:Code]]

Songbird: /* How does this relate to String Parsing? */

2017-08-15T18:08:24Z

How does this relate to String Parsing?

← Older revision		Revision as of 18:08, 15 August 2017
Line 16:		Line 16:
	String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute.		String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute.

	Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience ~~and not Mucker-level or higher staff~~ (who cannot edit MUF code in programs), String Parsing will be the focus.		Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience (who cannot edit MUF code in programs), String Parsing will be the focus.

	For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.		For the subsequent sections, please use the in-game @viewparse command to indent and colorize markup for better legibility.

Strongbird: /* Performance: Why should I care? */

2017-06-10T03:21:05Z

Performance: Why should I care?

← Older revision		Revision as of 03:21, 10 June 2017
Line 14:		Line 14:
	=== How does this relate to String Parsing? ===		=== How does this relate to String Parsing? ===

	String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute		String Parsing is a markup language found throughout many aspects of the game. From transformation messages, to sex scenes, to exploration, to NPC interaction, and more, String Parsing is used to provide fresh and dynamic content. As a result, it's important to ensure that this code is clean, readable, and swift to execute.

	Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.		Strictly speaking, a more important language to keep optimized is the MUF backend that Flexible Survival is based upon. However, since this guide is targeted at a general audience and not Mucker-level or higher staff (who cannot edit MUF code in programs), String Parsing will be the focus.

Strongbird at 03:19, 10 June 2017

2017-06-10T03:19:17Z

← Older revision		Revision as of 03:19, 10 June 2017
Line 1:		Line 1:
	<br> String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.		<br> String Parsing is a powerful language for designing content on the Flexible Survival MUCK. The language permits read functions, write functions, and allows users to create dynamic content based on a combination of those functions. Its semantics were originally designed by Damaged and later rewritten by Fauna for increased performance.

	String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code. ~~It will not tell you~~ how to write ~~clean or legible code, NOR will it teach you the fundamental markup of String Parsing. For information on those subjects~~, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.		String Parsing, like other markup languages, does cause a hit in performance when inserted into plain text. This article exists to provide solutions for those seeking to squeeze the most performance out of their code without reducing readability. For information on how to write parsing, see the wiki article on [http://wiki.flexiblesurvival.com/w/String_Parsing String Parsing] and review the in-game manual.

	<br>		<br>
Line 159:		Line 159:


	This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely ~~Songbird~~'s. Please only modify with either A), explicit permission to do so, or B), a fix for known factual inaccuracy / grammar errors.		This document is a work in progress and is thus subject to change. All views and opinions expressed in here are solely Songb's. Please only modify with either A) explicit permission to do so, or B) a fix for known factual inaccuracy / grammar errors.

	[[Category:Guides]][[Category:Code]]		[[Category:Guides]][[Category:Code]]

Strongbird: /* [one of][or][at random] */

2017-06-10T03:18:01Z

[one of][or][at random]

← Older revision		Revision as of 03:18, 10 June 2017
Line 117:		Line 117:
	::'''<span style="color:#FF0000">Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.		::'''<span style="color:#FF0000">Sometimes, a man's gotta man. [one of]Other times,[or]Sometimes,[at random] he doesn't.

	::'''<span style="color:#008000">Sometimes, a man's gotta man. [one of]Other [or]~~Some~~[at random]~~times~~, he doesn't.		::'''<span style="color:#008000">Sometimes, a man's gotta man. [one of]Other times[or]Sometimes[at random], he doesn't.


	In the above example, redundancy is ~~nixed~~ by moving a ~~string shared by all inputs~~ after [at random].		In the above example, redundancy is fixed by moving a comma after [at random].

Strongbird: /* [if ][else if ][else][end if] */

2017-06-10T03:13:23Z

[if ][else if ][else][end if]

← Older revision		Revision as of 03:13, 10 June 2017
Line 82:		Line 82:
	In the above example, a couple optimizations are made.		In the above example, a couple optimizations are made.

	Place [if time is night] at the front. This is the longest period of time and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.		Place [if time is night] at the front. This is the longest period of time outside of 'day' (which is not used here), and ensuring it triggers first saves execution costs throughout most of the 24-hour cycle. Use the check for 'afternoon' as the final [else], because even though it is just as long a period as morning and evening, the name has more characters in it.

	=== [case ] ===		=== [case ] ===

Strongbird: /* [if ][else][end if] */

2017-06-10T03:11:38Z

[if ][else][end if]

← Older revision		Revision as of 03:11, 10 June 2017
Line 48:		Line 48:
	----		----
	[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.		[else] creates potential for redundancy if a coder is not paying attention. Here is a small before-and-after list of sentences, followed by clear instruction.


	~~::'''<span style="color:#FF0000">[if time is winter]The large bear returned to his cave to hibernate.[else]The small fox jumped over the fence.[end if]~~

	~~::'''<span style="color:#008000">The [if time is winter]large bear returned to his cave to hibernat[else]small fox jumped over the fenc[end if]e.~~


	In the above example, repeated text has been removed from the [if ] statement itself and added as prefix and suffix to the code, respectively. This provides the exact same user-visible output with less characters and processing requirements.


Line 63:		Line 55:


	~~See~~ above~~. Repeated~~ text is removed from the [if ] statement itself and added as prefix and ~~suffix~~ to ~~the code~~, ~~respectively~~.		In the above example, repeated text has been removed from the [if ] statement itself and added as prefix. This provides the exact same user-visible output with less characters. Processing requirements are almost identical, but the text fits in less space and is just as readable.

			Note: It's generally preferred to not cut off letters in words. Punctuation can be moved outside, but chopping up words results in text that is much less legible to people with screen readers.
	<br>		<br>

Strongbird: /* Conditionals */

2017-06-10T03:05:27Z

Conditionals

← Older revision		Revision as of 03:05, 10 June 2017
Line 21:		Line 21:

	== Conditionals ==		== Conditionals ==

	~~Conditionals are the heart, brain, and skeletal structure of the String Parsing body.~~

	=== [if ][end if] ===		=== [if ][end if] ===