CreateLines (Stringlist function) - Revision history

JAL: /* Examples */

2012-10-31T15:22:11Z

Examples

← Older revision		Revision as of 15:22, 31 October 2012
Line 48:		Line 48:
	</p>		</p>

	In this example, the delimiter parameter (<code>$x2c('25')</code>) was really unnecessary because it's the default. In this example, one would presume that the socket is in <var>CHAR</var> mode, that is, data is being translated from EBCDIC to ASCII. Obviously, the <var>CreateLines</var> method does nothing that you could not do quite easily in <var class="product">User Language</var>. It is just a little more convenient and efficient.<li>The default behavior of <var>CreateLines</var> is to add a trailing delimiter. This default is based on the fact that most ASCII applications end the last line of a file with the line-end character(s), so they expect other applications to do the same. Still, the default can produce somewhat undesirable behavior, especially in interactions with <var>[[ParseLines ~~(Stringlist subroutine)\|ParseLines]]~~</var>.		In this example, the delimiter parameter (<code>$x2c('25')</code>) was really unnecessary because it's the default. In this example, one would presume that the socket is in <var>CHAR</var> mode, that is, data is being translated from EBCDIC to ASCII. Obviously, the <var>CreateLines</var> method does nothing that you could not do quite easily in <var class="product">User Language</var>. It is just a little more convenient and efficient.<li>The default behavior of <var>CreateLines</var> is to add a trailing delimiter. This default is based on the fact that most ASCII applications end the last line of a file with the line-end character(s), so they expect other applications to do the same. Still, the default can produce somewhat undesirable behavior, especially in interactions with <var>ParseLines</var>.
	In the following example, a string is created without a trailing line delimiter:		In the following example, a string is created without a trailing line delimiter:
	<p class="code">%sendString = %senddata:createLines($x2c('25'), addTrailingDelimiter=false)		<p class="code">%sendString = %senddata:createLines($x2c('25'), addTrailingDelimiter=false)

JAL2: /* Usage notes */

2012-05-15T16:23:21Z

Usage notes

← Older revision		Revision as of 16:23, 15 May 2012
Line 20:		Line 20:
	<ul>		<ul>
	<li>All errors in <var>CreateLines</var> result in request cancellation.		<li>All errors in <var>CreateLines</var> result in request cancellation.
	<li>The <var>[[ParseLines (~~Stringt~~ function)\|ParseLines]]</var> function performs the inverse operation; that is, it creates a <var>Stringlist</var> consisting of substrings bewteen an identified separator string.		<li>The <var>[[ParseLines (String function)\|ParseLines]]</var> function performs the inverse operation; that is, it creates a <var>Stringlist</var> consisting of substrings bewteen an identified separator string.
	</ul>		</ul>

JAL2: /* Usage notes */

2012-05-15T16:20:37Z

Usage notes

← Older revision		Revision as of 16:20, 15 May 2012
Line 20:		Line 20:
	<ul>		<ul>
	<li>All errors in <var>CreateLines</var> result in request cancellation.		<li>All errors in <var>CreateLines</var> result in request cancellation.
			<li>The <var>[[ParseLines (Stringt function)\|ParseLines]]</var> function performs the inverse operation; that is, it creates a <var>Stringlist</var> consisting of substrings bewteen an identified separator string.
	</ul>		</ul>

JAL2: /* See also */

2012-05-15T16:20:03Z

JAL2: /* Usage notes */

2012-05-15T16:18:43Z

Usage notes

← Older revision		Revision as of 16:18, 15 May 2012
Line 20:		Line 20:
	<ul>		<ul>
	<li>All errors in <var>CreateLines</var> result in request cancellation.		<li>All errors in <var>CreateLines</var> result in request cancellation.
	~~<li><var>CreateLines</var> is available in <var class="product">Sirius Mods</var> Version 6.7 and later.~~
	</ul>		</ul>

Dme: /* See also */

2012-05-15T15:26:18Z

JAL2: /* Syntax terms */

2012-03-19T20:01:24Z

Syntax terms

← Older revision		Revision as of 20:01, 19 March 2012
Line 8:		Line 8:
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>%string</th>		<tr><th>%string</th>
	<td>This ~~longstring~~ is to contain the data in <var class="term">sl</var>. </td></tr>		<td>This <var>Longstring</var> is to contain the data in <var class="term">sl</var>. </td></tr>
	<tr><th>sl</th>		<tr><th>sl</th>
	<td>A <var>Stringlist</var> object. </td></tr>		<td>A <var>Stringlist</var> object. </td></tr>

JALWiccan: 1 revision

2012-03-19T19:59:35Z

1 revision

← Older revision	Revision as of 19:59, 19 March 2012
(No difference)

JALWiccan: 1 revision

2012-03-19T19:59:34Z

1 revision

← Older revision		Revision as of 19:59, 19 March 2012
Line 48:		Line 48:
	</p>		</p>

	In this example, the delimiter parameter (<code>$x2c('25')</code>) was really unnecessary because it's the default. In this example, one would presume that the socket is in <var>CHAR</var> mode, that is, data is being translated from EBCDIC to ASCII. Obviously, the <var>CreateLines</var> method does nothing that you could not do quite easily in User Language. It is just a little more convenient and efficient.<li>The default behavior of <var>CreateLines</var> is to add a trailing delimiter. This default is based on the fact that most ASCII applications end the last line of a file with the line-end character(s), so they expect other applications to do the same. Still, the default can produce somewhat undesirable behavior, especially in interactions with <var>[[ParseLines (Stringlist subroutine)\|ParseLines]]</var>.		In this example, the delimiter parameter (<code>$x2c('25')</code>) was really unnecessary because it's the default. In this example, one would presume that the socket is in <var>CHAR</var> mode, that is, data is being translated from EBCDIC to ASCII. Obviously, the <var>CreateLines</var> method does nothing that you could not do quite easily in <var class="product">User Language</var>. It is just a little more convenient and efficient.<li>The default behavior of <var>CreateLines</var> is to add a trailing delimiter. This default is based on the fact that most ASCII applications end the last line of a file with the line-end character(s), so they expect other applications to do the same. Still, the default can produce somewhat undesirable behavior, especially in interactions with <var>[[ParseLines (Stringlist subroutine)\|ParseLines]]</var>.
	In the following example, a string is created without a trailing line delimiter:		In the following example, a string is created without a trailing line delimiter:
	<p class="code">%sendString = %senddata:createLines($x2c('25'), addTrailingDelimiter=false)		<p class="code">%sendString = %senddata:createLines($x2c('25'), addTrailingDelimiter=false)

JALWiccan: 1 revision

2011-04-13T22:33:39Z

1 revision

← Older revision	Revision as of 22:33, 13 April 2011
(No difference)

← Older revision		Revision as of 16:20, 15 May 2012
Line 54:		Line 54:

	==See also==		==See also==
	~~<ul>~~
	<li>The <var>[[ParseLines (Stringt function)\|ParseLines]]</var> function performs the inverse operation; that is, it creates a <var>Stringlist</var> consisting of substrings bewteen an identified separator string.
	~~</ul>~~
	{{Template:Stringlist:CreateLines footer}}		{{Template:Stringlist:CreateLines footer}}

← Older revision		Revision as of 15:26, 15 May 2012
Line 55:		Line 55:

	==See also==		==See also==
			<ul>
			<li>The <var>[[ParseLines (Stringt function)\|ParseLines]]</var> function performs the inverse operation; that is, it creates a <var>Stringlist</var> consisting of substrings bewteen an identified separator string.
			</ul>
	{{Template:Stringlist:CreateLines footer}}		{{Template:Stringlist:CreateLines footer}}