System classes and methods - Revision history

JAL: SOUL replaces UL

2016-05-16T20:16:26Z

SOUL replaces UL

← Older revision		Revision as of 20:16, 16 May 2016
Line 2:		Line 2:

	==Overview==		==Overview==
	The ability to define classes in <var class="product">~~User Language~~</var> is a powerful facility. However, some classes are likely to be extremely heavily accessed, require access to facilities not directly accessible in <var class="product">~~User Language~~</var>, or both. It is for such cases that '''system classes''' were created.		The ability to define classes in <var class="product">SOUL</var> is a powerful facility. However, some classes are likely to be extremely heavily accessed, require access to facilities not directly accessible in <var class="product">SOUL</var>, or both. It is for such cases that '''system classes''' were created.

	A system class is a class that is built into the <var class="product">[[Model 204]]</var> nucleus and is typically written in Assembler language. As such, these classes are very efficient and provide an object-oriented interface to the <var class="product">Model 204</var> kernel. Because these classes are not written in <var class="product">~~User Language~~</var>, however, the class definitions are not available in <var class="product">~~User Language~~</var>, so the documentation must be consulted to determine the methods available in each class.		A system class is a class that is built into the <var class="product">[[Model 204]]</var> nucleus and is typically written in Assembler language. As such, these classes are very efficient and provide an object-oriented interface to the <var class="product">Model 204</var> kernel. Because these classes are not written in <var class="product">SOUL</var>, however, the class definitions are not available in <var class="product">SOUL</var>, so the documentation must be consulted to determine the methods available in each class.

	Some system classes are available to all users licensed for version 7.5 or higher of <var class="product">Model 204</var>, and some system classes are tied to another product and so only available to users licensed for that product. For example, the system <var>Socket</var> class is only available to users licensed for <var class="product">[[Janus Sockets]]</var>.		Some system classes are available to all users licensed for version 7.5 or higher of <var class="product">Model 204</var>, and some system classes are tied to another product and so only available to users licensed for that product. For example, the system <var>Socket</var> class is only available to users licensed for <var class="product">[[Janus Sockets]]</var>.
Line 154:		Line 154:
	<table>		<table>
	<tr><th><var>[[Recordset class\|Recordset]]</var>, <var>[[Record class\|Record]]</var>, <var>[[SortedRecordset class\|SortedRecordset]]</var>, <var>[[RecordsetCursor class\|RecordsetCursor]]</var></th>		<tr><th><var>[[Recordset class\|Recordset]]</var>, <var>[[Record class\|Record]]</var>, <var>[[SortedRecordset class\|SortedRecordset]]</var>, <var>[[RecordsetCursor class\|RecordsetCursor]]</var></th>
	<td>Replace traditional <var class="product">~~User Language~~</var> file-oriented facilities.</td></tr>		<td>Replace traditional <var class="product">SOUL</var> file-oriented facilities.</td></tr>

	<tr><th><var>Socket</var></th>		<tr><th><var>Socket</var></th>

JAL: misc cleanup

2016-05-16T20:13:58Z

misc cleanup

← Older revision		Revision as of 20:13, 16 May 2016
Line 6:		Line 6:
	A system class is a class that is built into the <var class="product">[[Model 204]]</var> nucleus and is typically written in Assembler language. As such, these classes are very efficient and provide an object-oriented interface to the <var class="product">Model 204</var> kernel. Because these classes are not written in <var class="product">User Language</var>, however, the class definitions are not available in <var class="product">User Language</var>, so the documentation must be consulted to determine the methods available in each class.		A system class is a class that is built into the <var class="product">[[Model 204]]</var> nucleus and is typically written in Assembler language. As such, these classes are very efficient and provide an object-oriented interface to the <var class="product">Model 204</var> kernel. Because these classes are not written in <var class="product">User Language</var>, however, the class definitions are not available in <var class="product">User Language</var>, so the documentation must be consulted to determine the methods available in each class.

	Some system classes are available to all users licensed for ~~any Sirius Software product, and most system classes are available to all users licensed for~~ <var class="product">~~[[Janus SOAP]]~~</var>~~. However~~, some system classes are tied to another product and so only available to users licensed for that product. For example, the system <var>Socket</var> class is only available to users licensed for <var class="product">[[Janus Sockets]]</var>.		Some system classes are available to all users licensed for version 7.5 or higher of <var class="product">Model 204</var>, and some system classes are tied to another product and so only available to users licensed for that product. For example, the system <var>Socket</var> class is only available to users licensed for <var class="product">[[Janus Sockets]]</var>.

	All the system classes for which a user is authorized are available in any <var class="product">~~User Language~~</var> request and do not need to be declared. To use a system class, simply declare an object of that class. For example, the <var>[[Stringlist class\|Stringlist]]</var> class implements what is effectively an unbounded array of strings. To use this class, just declare a <var>Stringlist</var> object:		All the system classes for which a user is authorized are available in any <var class="product">SOUL</var> request and do not need to be declared. To use a system class, simply declare an object of that class. For example, the <var>[[Stringlist class\|Stringlist]]</var> class implements what is effectively an unbounded array of strings. To use this class, just declare a <var>Stringlist</var> object:
	<p class="code">%list is object stringlist		<p class="code">%list is object stringlist
	...		...
Line 27:		Line 27:

	There are already a large number of system classes, and their number is expected to grow over time.		There are already a large number of system classes, and their number is expected to grow over time.
	This raises the question of what happens when a new system class with the same name as a [[Classes and Objects\|~~User Language~~ class]] becomes available. For example, suppose there was already a ~~<var class="product">User Language</var>~~ <var>Stringlist</var> class when the system class of the same name became available. What would be made of the following code?		This raises the question of what happens when a new system class with the same name as a [[Classes and Objects\|user class]] becomes available. For example, suppose there was already a user-written <var>Stringlist</var> class when the system class of the same name became available. What would be made of the following code?
	<p class="code">class stringList		<p class="code">class stringList
	...		...
Line 34:		Line 34:
	%list is object stringList		%list is object stringList
	</p>		</p>
	The answer is that the code would continue to work as it had before. This is because it is perfectly valid to declare a ~~<var class="product">User Language</var>~~ class with the same name as a system class, and in such situations, all references to the class name are assumed to refer to the ~~<var class="product">User Language</var>~~ class. To access the system <var>Stringlist</var> class in this situation, you precede the class name with <code>system:</code> wherever it appears:		The answer is that the code would continue to work as it had before. This is because it is perfectly valid to declare a user class with the same name as a system class, and in such situations, all references to the class name are assumed to refer to the user class. To access the system <var>Stringlist</var> class in this situation, you precede the class name with <code>system:</code> wherever it appears:
	<p class="code">%systemList is object system:stringList		<p class="code">%systemList is object system:stringList
	...		...
	print %(system:Stringlist):maxItemLength		print %(system:Stringlist):maxItemLength
	</p>		</p>
	The <code>system:</code> prefix can be used, of course, regardless of whether a ~~<var class="product">User Language</var>~~ class by the same name exists. In fact, some sites may wish to adopt a local standard that all system class references must be preceded by <code>system:</code> to make clear what they are and to avoid confusion with ~~<var class="product">User Language</var>~~ classes. That said, it is probably best to avoid the names of system classes when declaring ~~<var class="product">User Language</var>~~ classes.		The <code>system:</code> prefix can be used, of course, regardless of whether a user class by the same name exists. In fact, some sites may wish to adopt a local standard that all system class references must be preceded by <code>system:</code> to make clear what they are and to avoid confusion with user-written classes. That said, it is probably best to avoid the names of system classes when declaring user classes.

	Except for the way they are defined, system classes behave exactly		Except for the way they are defined, system classes behave exactly
	like ~~<var class="product">User Language</var>~~ classes:		like user-written classes:
	<ul>		<ul>
	<li>Object variables are declared, constructed (New), and discarded in the same way.		<li>Object variables are declared, constructed (New), and discarded in the same way. </li>
	<li>Object variables of a system class can be declared inside a ~~<var~~ class~~="product">User Language~~</~~var~~> ~~class or structure.~~
	<li>Null tests and comparisons on system objects work the same way as for ~~<var class="product">User Language~~</~~var~~> ~~objects.~~		<li>Object variables of a system class can be declared inside a user class or structure. </li>
	<li>System object variables can be passed as parameters, and methods on system objects can be strung together.
			<li>Null tests and comparisons on system objects work the same way as for user objects. </li>

			<li>System object variables can be passed as parameters, and methods on system objects can be strung together. </li>
	</ul>		</ul>
	One distinction between ~~<var class="product">User Language</var>~~ classes and system classes is that the system		One distinction between user classes and system classes is that the system class methods do not have explicit declarations.
	class methods do not have explicit declarations.		So the only way to understand the return values and parameters to a system method is through the documentation.
	So the only way to understand the return values and parameters to a system
	method is through the documentation.

	For documentation purposes, all system method parameters and return values		For documentation purposes, all system method parameters and return values
	(or inputs and outputs) can be thought of as having one of four basic types:		(or inputs and outputs) can be thought of as having one of four basic types:

	<table ~~class="syntaxTable"~~>		<table>
	<tr><th><var>Object</var></th>		<tr><th><var>Object</var></th>
	<td>Some method outputs or inputs are objects of a particular class. The input and output classes will be specified in the documentation.</td></tr>		<td>Some method outputs or inputs are objects of a particular class. The input and output classes will be specified in the documentation.</td></tr>

	<tr><th><var>Float</var></th>		<tr><th><var>Float</var></th>
	<td>All numeric input and outputs can be thought of as being declared as <var>Float</var>. Of course, <var class="product">Model 204</var>'s handling of <var>Float</var> values makes a <var>Float</var> input or output suitable even where only integral values are expected.</td></tr>		<td>All numeric input and outputs can be thought of as being declared as <var>Float</var>. Of course, <var class="product">Model 204</var>'s handling of <var>Float</var> values makes a <var>Float</var> input or output suitable even where only integral values are expected.</td></tr>

	<tr><th><var>Longstring</var></th>		<tr><th><var>Longstring</var></th>
	<td>Any input or output that is a string, even if it is guaranteed to be shorter than 256 bytes should be considered a <var>[[Longstrings\|Longstring]]</var>. <var>Longstring</var> values are treated differently in certain expressions and have different truncation behavior than other <var>String</var> values — they will cause request cancellation if assigned to something that requires the <var>Longstring</var> to be truncated.</td></tr>		<td>Any input or output that is a string, even if it is guaranteed to be shorter than 256 bytes should be considered a <var>[[Longstrings\|Longstring]]</var>. <var>Longstring</var> values are treated differently in certain expressions and have different truncation behavior than other <var>String</var> values — they will cause request cancellation if assigned to something that requires the <var>Longstring</var> to be truncated.</td></tr>

	<tr><th><var>Unicode</var></th>		<tr><th><var>Unicode</var></th>
	<td>Identical to <var>Longstring</var> except the character set is considered to be the double-byte Unicode character set. <var>Unicode</var> variables and values are passed as Unicode parameters without any conversion, while all other values are converted to an EBCDIC string as needed, and then converted to <var>Unicode</var> using the Online's EBCDIC to Unicode translation tables. Any untranslatable EBCDIC string results in a request canceling error.		<td>Identical to <var>Longstring</var> except the character set is considered to be the double-byte Unicode character set. <var>Unicode</var> variables and values are passed as Unicode parameters without any conversion, while all other values are converted to an EBCDIC string as needed, and then converted to <var>Unicode</var> using the Online's EBCDIC to Unicode translation tables. Any untranslatable EBCDIC string results in a request canceling error.
Line 117:		Line 121:
	Unfortunately, if a second instance of the class were created,		Unfortunately, if a second instance of the class were created,
	the <code>$listnew</code> in the <code>New</code> constructor for the object would return the same $list identifier as		the <code>$listnew</code> in the <code>New</code> constructor for the object would return the same $list identifier as
	for the first instance, and it would cause any data in the $list for the first		for the first instance, and it would cause any data in the $list for the first instance to be deleted.
	instance to be deleted.

	Furthermore, since both objects would have the same $list identifier, they would		Furthermore, since both objects would have the same $list identifier, they would
Line 200:		Line 203:
	<div class="showVisit">		<div class="showVisit">
	<table class="wikitable">		<table class="wikitable">
	<tr><th>Method</th><th>Description</th></tr>		<tr class="head"><th>Method</th><th>Description</th></tr>

	<tr><td>[[U (String function)\|U function]]</td><td>Converts an EBCDIC string to a Unicode string </td></tr>		<tr><td>[[U (String function)\|U function]]</td><td>Converts an EBCDIC string to a Unicode string </td></tr>

	<tr><td>[[X (String function)\|X function]]</td><td>Returns the unencoded value of a hex-encoded string</td></tr>		<tr><td>[[X (String function)\|X function]]</td><td>Returns the unencoded value of a hex-encoded string</td></tr>
	</table>		</table>

JAL: /* Using system classes instead of $functions */ typos

2016-05-16T19:57:43Z

Using system classes instead of $functions: typos

← Older revision		Revision as of 19:57, 16 May 2016
Line 98:		Line 98:

	==Using system classes instead of $functions==		==Using system classes instead of $functions==
	There are several suites of $functions that are heavily used at many		There are several suites of $functions that are heavily used at many
	sites that "behave badly" in an object-oriented environment, especially inside non-shared methods.		sites that "behave badly" in an object-oriented environment, especially inside non-shared methods.
	For example, the [[$lists\|$list]] suite of $functions do not work well inside of methods.		For example, the [[$lists\|$list]] suite of $functions do not work well inside of methods.
Line 143:		Line 143:
	Finally, use of an object in this context makes it possible to		Finally, use of an object in this context makes it possible to
	take advantage of the better object-oriented syntax for "stringing" methods:		take advantage of the better object-oriented syntax for "stringing" methods:
	<p class="code">		<p class="code">%calculus is object section
	%calculus is object section
	...		...
	%calculus:list:add(%student)		%calculus:list:add(%student)
Line 150:		Line 149:

	The system classes that replace existing handle-based suites of $functions are:		The system classes that replace existing handle-based suites of $functions are:
	<table ~~class="syntaxTable"~~>		<table>
	<tr><th><var>[[Recordset class\|Recordset]]</var>, <var>[[Record class\|Record]]</var>, <var>[[SortedRecordset class\|SortedRecordset]]</var>, <var>[[RecordsetCursor class\|RecordsetCursor]]</var></th>		<tr><th><var>[[Recordset class\|Recordset]]</var>, <var>[[Record class\|Record]]</var>, <var>[[SortedRecordset class\|SortedRecordset]]</var>, <var>[[RecordsetCursor class\|RecordsetCursor]]</var></th>
	<td>Replace traditional <var class="product">User Language</var> file-oriented facilities.</td></tr>		<td>Replace traditional <var class="product">User Language</var> file-oriented facilities.</td></tr>

	<tr><th><var>Socket</var></th>		<tr><th><var>Socket</var></th>
	<td>Replaces $Sockets. Only available to licensees of ~~both~~ [[Janus Sockets~~]] and [[Janus SOAP~~]].</td></tr>		<td>Replaces $Sockets. Only available to licensees of [[Janus Sockets]].</td></tr>

	<tr><th><var>[[Stringlist class\|Stringlist]]</var></th>		<tr><th><var>[[Stringlist class\|Stringlist]]</var></th>
	<td>Replaces $~~Lists~~.</td></tr>		<td>Replaces $lists.</td></tr>

	<tr><th><var>[[XmlDoc class\|XmlDoc]]</var>, <var>[[XmlNode class\|XmlNode]]</var>, <var>[[XmlNodelist class\|XmlNodelist]]</var></th>		<tr><th><var>[[XmlDoc class\|XmlDoc]]</var>, <var>[[XmlNode class\|XmlNode]]</var>, <var>[[XmlNodelist class\|XmlNodelist]]</var></th>
	<td>Replace $XML_ $functions. Only available to licensees of [[Janus SOAP]].</td></tr>		<td>Replace $XML_ $functions. Only available to licensees of [[Janus SOAP]].</td></tr>

JALWiccan: Automatically generated page update

2013-10-14T20:05:31Z

Automatically generated page update

← Older revision		Revision as of 20:05, 14 October 2013
Line 205:		Line 205:


	[[Category:~~Janus SOAP ULI~~ topics]]		[[Category:SOUL object-oriented programming topics]]

JAL at 16:14, 11 October 2012

2012-10-11T16:14:33Z

← Older revision		Revision as of 16:14, 11 October 2012
Line 152:		Line 152:
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th><var>[[Recordset class\|Recordset]]</var>, <var>[[Record class\|Record]]</var>, <var>[[SortedRecordset class\|SortedRecordset]]</var>, <var>[[RecordsetCursor class\|RecordsetCursor]]</var></th>		<tr><th><var>[[Recordset class\|Recordset]]</var>, <var>[[Record class\|Record]]</var>, <var>[[SortedRecordset class\|SortedRecordset]]</var>, <var>[[RecordsetCursor class\|RecordsetCursor]]</var></th>
	<td>Replace traditional User Language file-oriented facilities.</td></tr>		<td>Replace traditional <var class="product">User Language</var> file-oriented facilities.</td></tr>
	<tr><th><var>Socket</var></th>		<tr><th><var>Socket</var></th>
	<td>Replaces $Sockets. Only available to licensees of both [[Janus Sockets]] and [[Janus SOAP]].</td></tr>		<td>Replaces $Sockets. Only available to licensees of both [[Janus Sockets]] and [[Janus SOAP]].</td></tr>

JAL2: /* Overview */

2012-03-09T21:41:57Z

Overview

← Older revision		Revision as of 21:41, 9 March 2012
Line 6:		Line 6:
	A system class is a class that is built into the <var class="product">[[Model 204]]</var> nucleus and is typically written in Assembler language. As such, these classes are very efficient and provide an object-oriented interface to the <var class="product">Model 204</var> kernel. Because these classes are not written in <var class="product">User Language</var>, however, the class definitions are not available in <var class="product">User Language</var>, so the documentation must be consulted to determine the methods available in each class.		A system class is a class that is built into the <var class="product">[[Model 204]]</var> nucleus and is typically written in Assembler language. As such, these classes are very efficient and provide an object-oriented interface to the <var class="product">Model 204</var> kernel. Because these classes are not written in <var class="product">User Language</var>, however, the class definitions are not available in <var class="product">User Language</var>, so the documentation must be consulted to determine the methods available in each class.

	Some system classes are available to all ~~useres license~~ for any Sirius Software product, and most system classes are available to all users licensed for <var class="product">[[Janus SOAP]]</var>. However, some system classes are tied to another product and so only available to users licensed for that product. For example, the system Socket class is only available to users licensed for <var class="product">[[Janus Sockets]]</var>.		Some system classes are available to all users licensed for any Sirius Software product, and most system classes are available to all users licensed for <var class="product">[[Janus SOAP]]</var>. However, some system classes are tied to another product and so only available to users licensed for that product. For example, the system <var>Socket</var> class is only available to users licensed for <var class="product">[[Janus Sockets]]</var>.

	All the system classes for which a user is authorized are available in any <var class="product">User Language</var> request and do not need to be declared. To use a system class, simply declare an object of that class. For example, the <var>[[Stringlist class\|Stringlist]]</var> class implements what is effectively an unbounded array of strings. To use this class, just declare a <var>Stringlist</var> object:		All the system classes for which a user is authorized are available in any <var class="product">User Language</var> request and do not need to be declared. To use a system class, simply declare an object of that class. For example, the <var>[[Stringlist class\|Stringlist]]</var> class implements what is effectively an unbounded array of strings. To use this class, just declare a <var>Stringlist</var> object:
	<p class="code">		<p class="code">%list is object stringlist
	%list is object stringlist
	...		...
	%list = new		%list = new
Line 17:		Line 16:
	</p>		</p>
	Some system classes have shared methods and, like user classes,		Some system classes have shared methods and, like user classes,
	these can be accessed with any object of the class or with the		these can be accessed with any object of the class or with the class name in parentheses.
	class name in parentheses.		For example, the <var>[[MaxItemLength (Stringlist property)\|MaxItemLength]]</var> property in the <var>Stringlist</var> class
	For example, the [[MaxItemLength (Stringlist property)\|MaxItemLength ~~poperty~~]] in the <var>Stringlist</var> class
	returns the maximum length of any <var>Stringlist</var> item.		returns the maximum length of any <var>Stringlist</var> item.
	Since this length does not depend on a particular instance, it is a shared method and can be accessed as such:		Since this length does not depend on a particular instance, it is a shared method and can be accessed as such:
Line 33:		Line 31:
	...		...
	end class		end class
	...		...
	%list is object stringList		%list is object stringList
	</p>		</p>
Line 58:		Line 56:
	For documentation purposes, all system method parameters and return values		For documentation purposes, all system method parameters and return values
	(or inputs and outputs) can be thought of as having one of four basic types:		(or inputs and outputs) can be thought of as having one of four basic types:

	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th><var>Object</var></th>		<tr><th><var>Object</var></th>
Line 68:		Line 67:
	<td>Identical to <var>Longstring</var> except the character set is considered to be the double-byte Unicode character set. <var>Unicode</var> variables and values are passed as Unicode parameters without any conversion, while all other values are converted to an EBCDIC string as needed, and then converted to <var>Unicode</var> using the Online's EBCDIC to Unicode translation tables. Any untranslatable EBCDIC string results in a request canceling error.		<td>Identical to <var>Longstring</var> except the character set is considered to be the double-byte Unicode character set. <var>Unicode</var> variables and values are passed as Unicode parameters without any conversion, while all other values are converted to an EBCDIC string as needed, and then converted to <var>Unicode</var> using the Online's EBCDIC to Unicode translation tables. Any untranslatable EBCDIC string results in a request canceling error.
	</table>		</table>
	The one exception to this simple picture is the ''Item'' input and output from [[Collections\|collection classes]].
			The one exception to this simple picture is the <var>Item</var> input and output from [[Collections\|collection classes]].
	Methods in collection classes behave as if any item input or output		Methods in collection classes behave as if any item input or output
	was an assignment to or from the item class type.		was an assignment to or from the item class type.

JAL2 at 21:32, 9 March 2012

2012-03-09T21:32:55Z

Show changes

JAL2: /* Constant methods */

2012-03-09T20:59:24Z

Constant methods

@@ Line 210: / Line 210: @@
 Thus, <code>'0d25':x</code> is basically a hex constant.
-The individual Constant methods are described in the following subsections.
+The following are the available Constant methods:
-===X function===
+<div class="showVisit">
+<table class="wikitable">
-This function returns the unencoded value of a hex-encoded string.
+<tr><th>Method</th><th>Description</th></tr>
-It treats each input character as an input hex digit.
+<tr><td>[[U (String function)|U function]]</td><td>Converts an EBCDIC string to a Unicode string </td></tr>
+<tr><td>[[X (String function)|X function]]</td><td>Returns the unencoded value of a hex-encoded string</td></tr>
 </table>
-====Usage Notes====
+</div>
 [[Category:Janus SOAP ULI topics]]

JAL2: /* Syntax Terms */

2012-02-22T16:23:59Z

Syntax Terms

JAL2 at 20:33, 17 February 2012

2012-02-17T20:33:20Z

← Older revision		Revision as of 20:33, 17 February 2012
Line 303:		Line 303:
	to a byte-stream Longstring, which the StringToHex method converts to its		to a byte-stream Longstring, which the StringToHex method converts to its
	hex representation.		hex representation.

			[[Category:Janus SOAP ULI topics]]

← Older revision		Revision as of 16:23, 22 February 2012
Line 260:		Line 260:
	<td>A constant character string value, which may include an XML-style hexadecimal character reference or an XHTML entity reference. That is, ''string'' may contain an ampersand (&) in the following cases:		<td>A constant character string value, which may include an XML-style hexadecimal character reference or an XHTML entity reference. That is, ''string'' may contain an ampersand (&) in the following cases:
	<ul>		<ul>
	<li>As the substring '&amp;'.		<li>As the substring <code>&amp;</code>.
	This substring is converted to a single ampersand character.		This substring is converted to a single ampersand character.
	<li>At the start of a hexadecimal character reference (for example, the eight characters		<li>At the start of a hexadecimal character reference (for example, the eight characters
	'&#x201C;' for the Unicode "Left double quotation mark").		<code>&#x201C;</code> for the Unicode "Left double quotation mark").
	The character reference is converted to the referenced character.		The character reference is converted to the referenced character.
	<li>As of [[Sirius Mods]] version 7.6, an XHTML entity reference (for example,		<li>As of [[Sirius Mods]] version 7.6, an XHTML entity reference (for example,
	the six characters '&nbsp;' for the "non-breaking-space" character).		the six characters <code>&nbsp;</code> for the "non-breaking-space" character).
	The entity reference is converted to the referenced character.		The entity reference is converted to the referenced character.
	</ul>		</ul>
	A decimal character reference (for example, '&#172;') is ''not'' allowed.</td></tr>		A decimal character reference (for example, <code>&#172;</code>) is ''not'' allowed.</td></tr>
	</table>		</table>

	====Usage Notes====		====Usage Notes====
	<ul>		<ul>