COMPOPT parameter - Revision history

Goff: /* Description */

2024-11-24T20:50:18Z

Description

← Older revision		Revision as of 20:50, 24 November 2024
Line 29:		Line 29:

	<tr><th>X'08'</th>		<tr><th>X'08'</th>
	<td>Only applicable in ~~for~~ Model 204 8.0 to enable transparency mode.		<td>Only applicable in Model 204 8.0 to enable transparency mode.
	<p>Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every global image. So, if a large global image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that image's FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. The amount of extra space required is 7 bytes for each image item plus the sum of the length of the names of the image items.</p>		<p>Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every global image. So, if a large global image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that image's FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. The amount of extra space required is 7 bytes for each image item plus the sum of the length of the names of the image items.</p>
	<p>If the image is not global, any increase might also increase runtime FSCB usage, and if it’s global it will increase runtime GTBL usage.</p></td></tr>		<p>If the image is not global, any increase might also increase runtime FSCB usage, and if it’s global it will increase runtime GTBL usage.</p></td></tr>

Goff: Update to reflect 00982784 fix

2024-10-20T21:20:39Z

Update to reflect 00982784 fix

← Older revision		Revision as of 21:20, 20 October 2024
Line 30:		Line 30:
	<tr><th>X'08'</th>		<tr><th>X'08'</th>
	<td>Only applicable in for Model 204 8.0 to enable transparency mode.		<td>Only applicable in for Model 204 8.0 to enable transparency mode.
	<p>Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every image. So, if a large image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that ~~images~~ FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. The amount of extra space required is 7 bytes for each image item plus the sum of the length of the names of the image items.</p>		<p>Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every global image. So, if a large global image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that image's FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. The amount of extra space required is 7 bytes for each image item plus the sum of the length of the names of the image items.</p>
	<p>If the image is not global, any increase might also increase runtime FSCB usage, and if it’s global it will increase runtime GTBL usage.</p></td></tr>		<p>If the image is not global, any increase might also increase runtime FSCB usage, and if it’s global it will increase runtime GTBL usage.</p></td></tr>
	</table>		</table>

Goff: NAMESAVE increases to FSCB

2024-10-18T04:41:55Z

NAMESAVE increases to FSCB

← Older revision		Revision as of 04:41, 18 October 2024
Line 30:		Line 30:
	<tr><th>X'08'</th>		<tr><th>X'08'</th>
	<td>Only applicable in for Model 204 8.0 to enable transparency mode.		<td>Only applicable in for Model 204 8.0 to enable transparency mode.
	<p>		<p>Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every image. So, if a large image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that images FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. The amount of extra space required is 7 bytes for each image item plus the sum of the length of the names of the image items.</p>
	Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every image. So, if a large image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that images FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. </p></td></tr>		<p>If the image is not global, any increase might also increase runtime FSCB usage, and if it’s global it will increase runtime GTBL usage.</p></td></tr>
	</table>		</table>

Goff: Add COMPOPT X'08'

2024-10-18T03:29:18Z

Add COMPOPT X'08'

← Older revision		Revision as of 03:29, 18 October 2024
Line 27:		Line 27:
	<p>		<p>
	Setting the <var>COMPOPT</var> X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without <var>Sirius Case ToUpper</var> in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications. </p></td></tr>		Setting the <var>COMPOPT</var> X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without <var>Sirius Case ToUpper</var> in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications. </p></td></tr>

			<tr><th>X'08'</th>
			<td>Only applicable in for Model 204 8.0 to enable transparency mode.
			<p>
			Setting the <var>COMPOPT</var> X'08' bit applies an implicit NAMESAVE to every image. So, if a large image did not have NAMESAVE specified, but COMPOPT X’08’ is set, that images FSCB requirements will go up at runtime. Otherwise, there should be no change to FSCB requirements. </p></td></tr>
	</table>		</table>

JAL: misc formatting

2016-09-01T22:08:21Z

misc formatting

← Older revision		Revision as of 22:08, 1 September 2016
Line 13:		Line 13:
	<dd>Before Sirius Mods 6.7		<dd>Before Sirius Mods 6.7
	</dl>		</dl>

	==Description==		==Description==
	~~As of Sirius Mods version 6.8, the~~ system parameter COMPOPT facilitates migration to [[Mixed-case SOUL\|mixed-case SOUL]]. COMPOPT is a <var class="product">Model 204</var> bitmask parameter that must be set in the CCAIN (User 0 input) stream. The bits in COMPOPT have the following meanings:		The system parameter <var>COMPOPT</var> facilitates migration to [[Mixed-case SOUL\|mixed-case SOUL]]. <var>COMPOPT</var> is a <var class="product">Model 204</var> bitmask parameter that must be set in the CCAIN (User 0 input) stream. The bits in <var>COMPOPT</var> have the following meanings:
	; X'01'		<table class="thJustBold">
	: If on, all procedures start out in Sirius Case ToUpper mode, whether or not they begin with a mixed-case Begin statement. Sirius Case ToUpper mode translates all unquoted tokens to uppercase, so <var class="product">SOUL</var> statements, keywords, variable names, etc. may be written in mixed case. By setting the COMPOPT X'01' bit, a site is essentially enabling mixed-case SOUL almost everywhere.		<tr><th>X'01'</th>
	; X'02'		<td>If on, all procedures start out in <var>[[Sirius Case statement#sirCaseStmt\|Sirius Case ToUpper]]</var> mode, whether or not they begin with a mixed-case <var>Begin</var> statement. <var>Sirius Case ToUpper</var> mode translates all unquoted tokens to uppercase, so <var class="product">SOUL</var> statements, keywords, variable names, etc. may be written in mixed case. By setting the <var>COMPOPT</var> X'01' bit, a site is essentially enabling mixed-case SOUL almost everywhere. </td></tr>
	: If on, Sirius Case Leave compiler directives are to be ignored: if Sirius Case ToUpper is in effect, it remains in effect even if a Sirius Case Leave directive is encountered. Setting the COMPOPT X'02' bit along with the X'01' bit enables mixed-case SOUL everywhere, thus ensuring consistent language processing throughout an Online.
	; X'04'		<tr><th>X'02'</th>
	: If on, image or image-item names, either literal or in variables, are to be automatically converted to uppercase before being used in methods or $functions. Since mixed-case SOUL is accomplished by translating unquoted tokens to uppercase, this case conversion for image or image-item names is the runtime equivalent of the compiler mixed-case support.<~~br /~~><br />~~Setting the COMPOPT~~ X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without Sirius Case ToUpper in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications.		<td>If on, <var>Sirius Case Leave</var> compiler directives are to be ignored: if <var>Sirius Case ToUpper</var> is in effect, it remains in effect even if a <var>Sirius Case Leave</var> directive is encountered. Setting the <var>COMPOPT</var> X'02' bit along with the X'01' bit enables mixed-case SOUL everywhere, thus ensuring consistent language processing throughout an Online. </td></tr>

			<tr><th>X'04'</th>
			<td>If on, image or image-item names, either literal or in variables, are to be automatically converted to uppercase before being used in methods or $functions. Since mixed-case SOUL is accomplished by translating unquoted tokens to uppercase, this case conversion for image or image-item names is the runtime equivalent of the compiler mixed-case support.
			<p>
			Setting the <var>COMPOPT</var> X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without <var>Sirius Case ToUpper</var> in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications. </p></td></tr>
			</table>

	==See also==		==See also==
	<ul>		<ul>
	<li>~~The~~ <var>[[SIRCOMP parameter\|SIRCOMP]]</var> ~~parameter.~~		<li><var>[[SIRCOMP parameter\|SIRCOMP]]</var>
	</ul>		</ul>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Dme: /* Description */

2015-01-23T21:08:27Z

Description

← Older revision		Revision as of 21:08, 23 January 2015
Line 21:		Line 21:
	; X'04'		; X'04'
	: If on, image or image-item names, either literal or in variables, are to be automatically converted to uppercase before being used in methods or $functions. Since mixed-case SOUL is accomplished by translating unquoted tokens to uppercase, this case conversion for image or image-item names is the runtime equivalent of the compiler mixed-case support.<br /><br />Setting the COMPOPT X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without Sirius Case ToUpper in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications.		: If on, image or image-item names, either literal or in variables, are to be automatically converted to uppercase before being used in methods or $functions. Since mixed-case SOUL is accomplished by translating unquoted tokens to uppercase, this case conversion for image or image-item names is the runtime equivalent of the compiler mixed-case support.<br /><br />Setting the COMPOPT X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without Sirius Case ToUpper in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications.
			==See also==
			<ul>
			<li>The <var>[[SIRCOMP parameter\|SIRCOMP]]</var> parameter.
			</ul>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Dme at 21:49, 22 January 2015

2015-01-22T21:49:43Z

← Older revision		Revision as of 21:49, 22 January 2015
Line 14:		Line 14:
	</dl>		</dl>
	==Description==		==Description==
	As of Sirius Mods version 6.8, the system parameter COMPOPT facilitates migration to [[Mixed-case ~~User Language~~\|mixed-case ~~User Language~~]]. COMPOPT is a <var class="product">Model 204</var> bitmask parameter that must be set in the CCAIN (User 0 input) stream. The bits in COMPOPT have the following meanings:		As of Sirius Mods version 6.8, the system parameter COMPOPT facilitates migration to [[Mixed-case SOUL\|mixed-case SOUL]]. COMPOPT is a <var class="product">Model 204</var> bitmask parameter that must be set in the CCAIN (User 0 input) stream. The bits in COMPOPT have the following meanings:
	; X'01'		; X'01'
	: If on, all procedures start out in Sirius Case ToUpper mode, whether or not they begin with a mixed-case Begin statement. Sirius Case ToUpper mode translates all unquoted tokens to uppercase, so <var class="product">~~User Language~~</var> statements, keywords, variable names, etc. may be written in mixed case. By setting the COMPOPT X'01' bit, a site is essentially enabling mixed-case ~~User Language~~ almost everywhere.		: If on, all procedures start out in Sirius Case ToUpper mode, whether or not they begin with a mixed-case Begin statement. Sirius Case ToUpper mode translates all unquoted tokens to uppercase, so <var class="product">SOUL</var> statements, keywords, variable names, etc. may be written in mixed case. By setting the COMPOPT X'01' bit, a site is essentially enabling mixed-case SOUL almost everywhere.
	; X'02'		; X'02'
	: If on, Sirius Case Leave compiler directives are to be ignored: if Sirius Case ToUpper is in effect, it remains in effect even if a Sirius Case Leave directive is encountered. Setting the COMPOPT X'02' bit along with the X'01' bit enables mixed-case ~~User Language~~ everywhere, thus ensuring consistent language processing throughout an Online.		: If on, Sirius Case Leave compiler directives are to be ignored: if Sirius Case ToUpper is in effect, it remains in effect even if a Sirius Case Leave directive is encountered. Setting the COMPOPT X'02' bit along with the X'01' bit enables mixed-case SOUL everywhere, thus ensuring consistent language processing throughout an Online.
	; X'04'		; X'04'
	: If on, image or image-item names, either literal or in variables, are to be automatically converted to uppercase before being used in methods or $functions. Since mixed-case ~~User Language~~ is accomplished by translating unquoted tokens to uppercase, this case conversion for image or image-item names is the runtime equivalent of the compiler mixed-case support.<br /><br />Setting the COMPOPT X'04' bit enables image and image-item names that appear as literals in ~~User Language~~ programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without Sirius Case ToUpper in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications.		: If on, image or image-item names, either literal or in variables, are to be automatically converted to uppercase before being used in methods or $functions. Since mixed-case SOUL is accomplished by translating unquoted tokens to uppercase, this case conversion for image or image-item names is the runtime equivalent of the compiler mixed-case support.<br /><br />Setting the COMPOPT X'04' bit enables image and image-item names that appear as literals in SOUL programs to be entered in mixed case. The only time this might be a problem is if there are true mixed-case image or image-item names in an application. A true mixed-case image or image-item name is one written in mixed case, either inside quotation marks (image and image-item names can indeed be put in quotes) or without Sirius Case ToUpper in effect. In general, neither of these is too likely, so true mixed-case image or image-item names are not likely in most applications.

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:25:28Z

Automatically generated page update

← Older revision		Revision as of 16:25, 27 August 2013
Line 1:		Line 1:
			{{Template:COMPOPT parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

Alex at 17:39, 21 February 2013

2013-02-21T17:39:02Z

← Older revision		Revision as of 17:39, 21 February 2013
Line 13:		Line 13:
	</dl>		</dl>
	==Description==		==Description==
			As of Sirius Mods version 6.8, the system parameter COMPOPT facilitates migration to [[Mixed-case User Language\|mixed-case User Language]]. COMPOPT is a <var class="product">Model 204</var> bitmask parameter that must be set in the CCAIN (User 0 input) stream. The bits in COMPOPT have the following meanings:
	As of Sirius Mods version 6.8, the system parameter COMPOPT facilitates migration to mixed-case User Language. COMPOPT is a <var class="product">Model 204</var> bitmask parameter that must be set in the CCAIN (User 0 input) stream. The bits in COMPOPT have the following meanings:

	; X'01'		; X'01'
	: If on, all procedures start out in Sirius Case ToUpper mode, whether or not they begin with a mixed-case Begin statement. Sirius Case ToUpper mode translates all unquoted tokens to uppercase, so <var class="product">User Language</var> statements, keywords, variable names, etc. may be written in mixed case. By setting the COMPOPT X'01' bit, a site is essentially enabling mixed-case User Language almost everywhere.		: If on, all procedures start out in Sirius Case ToUpper mode, whether or not they begin with a mixed-case Begin statement. Sirius Case ToUpper mode translates all unquoted tokens to uppercase, so <var class="product">User Language</var> statements, keywords, variable names, etc. may be written in mixed case. By setting the COMPOPT X'01' bit, a site is essentially enabling mixed-case User Language almost everywhere.

JALWiccan: 1 revision

2012-11-08T21:52:43Z

1 revision

← Older revision	Revision as of 21:52, 8 November 2012
(No difference)