Intrinsic classes - Revision history

JAL: change table class

2016-04-13T21:27:50Z

change table class

← Older revision		Revision as of 21:27, 13 April 2016
Line 162:		Line 162:

	Intrinsic methods can be further classified into these subsets:		Intrinsic methods can be further classified into these subsets:
	<table class="~~list~~">		<table class="thJustBold">
	<tr><th>Float</th><td>Methods that perform numeric manipulation on values in <var class="product">Model 204</var>'s <var>Float</var> format.</td></tr>		<tr><th>Float</th>
			<td>Methods that perform numeric manipulation on values in <var class="product">Model 204</var>'s <var>Float</var> format.</td></tr>

	<tr><th>Fixed</th><td>Methods that perform numeric manipulation on values in <var class="product">Model 204</var>'s <var>Fixed</var> format (with an assumed DP of 0).</td></tr>		<tr><th>Fixed</th>
			<td>Methods that perform numeric manipulation on values in <var class="product">Model 204</var>'s <var>Fixed</var> format (with an assumed DP of 0).</td></tr>

	<tr><th>String</th><td>Methods that perform string manipulation, with <var>Longstring</var> capability assumed.</td></tr>		<tr><th>String</th>
			<td>Methods that perform string manipulation, with <var>Longstring</var> capability assumed.</td></tr>

	<tr><th>Unicode</th><td>Methods that perform Unicode string manipulation, return Unicode results, or are based on the [[Unicode#Support for the ASCII subset of Unicode\|Unicode tables]].</td></tr>		<tr><th>Unicode</th><td>Methods that perform Unicode string manipulation, return Unicode results, or are based on the [[Unicode#Support for the ASCII subset of Unicode\|Unicode tables]].</td></tr>

JAL: minor cleanup

2016-03-18T16:00:10Z

minor cleanup

← Older revision		Revision as of 16:00, 18 March 2016
Line 429:		Line 429:

	So it is recommended that you discontinue the use of the <var>Print</var>, <var>Audit</var>, and		So it is recommended that you discontinue the use of the <var>Print</var>, <var>Audit</var>, and
	<var>Trace</var> statements in favor of <var>PrintText</var>, <var>AuditText</var>, and <var>TraceText</var>~~, as of <var class="product">Sirius Mods</var>~~		<var>Trace</var> statements in favor of <var>PrintText</var>, <var>AuditText</var>, and <var>TraceText</var>.
	~~7.2~~.

	==See also==		==See also==

JAL: minor cleanup

2016-03-18T15:57:35Z

minor cleanup

← Older revision		Revision as of 15:57, 18 March 2016
Line 88:		Line 88:
	efficiency anyway.		efficiency anyway.

	<table class="~~list~~">		<table class="thJustBold">
	<tr><th>Float</th><td>See [[List of Float methods~~\|"List of Float methods"~~]]</td></tr>		<tr><th>Float</th>
	<tr><th>String</th><td>See [[List of String methods~~\|"List of String methods"~~]]</td></tr>		<td>See [[List of Float methods]]</td></tr>
	<tr><th>Unicode</th><td>See [[List of Unicode methods~~\|"List of Unicode methods"~~]]</td></tr>
			<tr><th>String</th>
			<td>See [[List of String methods]]</td></tr>

			<tr><th>Unicode</th>
			<td>See [[List of Unicode methods]]</td></tr>
	</table>		</table>

Line 98:		Line 103:
	Beyond the internal representation of strings and numbers, a distinction between <var class="product">SOUL</var> and pure object-oriented languages was that the <var class="term">object</var>:<var class="term">method</var> syntax		Beyond the internal representation of strings and numbers, a distinction between <var class="product">SOUL</var> and pure object-oriented languages was that the <var class="term">object</var>:<var class="term">method</var> syntax
	was not used to manipulate strings and numbers; instead, strings and numbers were		was not used to manipulate strings and numbers; instead, strings and numbers were
	manipulated via $functions. ~~<var class="product">Sirius Mods</var> 7.2~~ changed ~~this~~ to allow the <var class="term">object</var>:<var class="term">method</var>		manipulated via $functions. This was changed to allow the <var class="term">object</var>:<var class="term">method</var>
	syntax against string and numeric variables and constants.		syntax against string and numeric variables and constants.

	The following code fragment illustrates how the same operation can be accomplished ~~via~~		The following code fragment illustrates how the same operation can be accomplished with
	traditional $functions and ~~via~~ object-oriented syntax:		traditional $functions and with object-oriented syntax:
	<p class="code">%name is string len 32		<p class="code">%name is string len 32
	...		...
Line 147:		Line 152:
	It is worth pointing out, however, that loose-datatyping between strings and numbers		It is worth pointing out, however, that loose-datatyping between strings and numbers
	does not imply loose-datatyping between strings and numbers and other classes. That		does not imply loose-datatyping between strings and numbers and other classes. That
	is, there are generally no implicit conversions of strings or numbers to or from non-string,		is, there are generally no implicit conversions of strings or numbers to or from non-string, non-numeric objects.
	non-numeric objects.

	Because loose-datatyping and the existing <var class="product">SOUL</var> datatypes work quite well in		Because loose-datatyping and the existing <var class="product">SOUL</var> datatypes work quite well in
	facilitating rapid development of reasonably tight and efficient code, ~~the <var class="product">[[Janus SOAP~~		facilitating rapid development of reasonably tight and efficient code, support for methods against string and numeric types does not add any new
	~~ULI]]</var>~~ support for methods against string and numeric types does not add any new
	datatypes to <var class="product">SOUL</var>. And, because of loose-datatyping, the numeric and string		datatypes to <var class="product">SOUL</var>. And, because of loose-datatyping, the numeric and string
	methods can be applied to any of the standard <var class="product">SOUL</var> string and numeric		methods can be applied to any of the standard <var class="product">SOUL</var> string and numeric
Line 243:		Line 246:
	</p>		</p>

	==Automatic ~~“~~implicit~~”~~ conversion of intrinsic values==		==Automatic "implicit" conversion of intrinsic values==
	As with other methods, the colon that separates the intrinsic method object from the method		As with other methods, the colon that separates the intrinsic method object from the method
	name can be optionally preceded or followed by spaces. This could be done to enhance		name can be optionally preceded or followed by spaces. This could be done to enhance
Line 255:		Line 258:
	different type than the datatype on which the method operates, the input value is		different type than the datatype on which the method operates, the input value is
	automatically converted into the target datatype. For example, the expression <code>7/3</code>		automatically converted into the target datatype. For example, the expression <code>7/3</code>
	clearly produces a numeric value, but the <var>Left</var> method operates on strings. So, in the		clearly produces a numeric value, but the <var>Left</var> method operates on strings. So, in the following statement:
	statement:
	<p class="code">%i = (7/3):left(4) </p>		<p class="code">%i = (7/3):left(4) </p>

	~~the~~ result of the division is converted into a string and then passed to <var>Left</var>, which		The result of the division is converted into a string and then passed to <var>Left</var>, which
	produces <code>2.33</code> as its result.		produces <code>2.33</code> as its result.

Line 350:		Line 352:
	<div id="printtext"></div>		<div id="printtext"></div>
	===Intrinsic methods in a Print, Audit, or Trace statement===		===Intrinsic methods in a Print, Audit, or Trace statement===
	The <var class="product">SOUL</var> <var>Print</var>, <var>Audit</var>, and <var>Trace</var> statements all use somewhat unusual		The <var class="product">SOUL</var> <var>Print</var>, <var>Audit</var>, and <var>Trace</var> statements all use somewhat unusual syntax.
	syntax.
	While initially these statements appear to operate		While initially these statements appear to operate
	on expressions, just like an assignment, this is not really the case.		on expressions, just like an assignment, this is not really the case.
Line 395:		Line 396:
	</ul>		</ul>

	Fortunately, ~~<var class="product">Sirius Mods</var> version 7.2, the same version that introduced intrinsic~~		Fortunately, the newer '''PrintText''', '''AuditText''',
	~~methods, also introduced~~ the '''PrintText''', '''AuditText''',		and '''TraceText''' statements (see [[Targeted Text statements]]) are direct analogs of <var>Print</var>, <var>Audit</var>, and <var>Trace</var>, respectively, but they use
	and '''TraceText''' statements (see [[Targeted Text statements~~\|"Targeted Text statements"~~]]).
	~~These~~ are direct analogs of <var>Print</var>, <var>Audit</var>, and <var>Trace</var>, respectively, but they use
	a more consistent syntax.		a more consistent syntax.
	Specifically, the newer statements treat everything as literal text, except		Specifically, the newer statements treat everything as literal text, except

JAL at 00:00, 11 October 2014

2014-10-11T00:00:50Z

← Older revision		Revision as of 00:00, 11 October 2014
Line 4:		Line 4:
	*[[List of Unicode methods]]		*[[List of Unicode methods]]
	*[[List of Intrinsic methods]]		*[[List of Intrinsic methods]]


	===Definition of Intrinsic classes===		===Definition of Intrinsic classes===

JAL at 23:59, 10 October 2014

2014-10-10T23:59:40Z

← Older revision		Revision as of 23:59, 10 October 2014
Line 270:		Line 270:
	<var>Unicode</var> method.		<var>Unicode</var> method.

	'''Note:''' Because some EBCDIC characters are not translatable to Unicode, and vice		<p class="note">'''Note:''' Because some EBCDIC characters are not translatable to Unicode, and vice
	versa, automatic conversions involving Unicode values may cause request cancellation.		versa, automatic conversions involving Unicode values may cause request cancellation.
	The explicit intrinsic conversion methods (like <var>EbcdicToUnicode</var> and <var>EbcdicToAscii</var> and		The explicit intrinsic conversion methods (like <var>EbcdicToUnicode</var> and <var>EbcdicToAscii</var> and
	their counterparts <var>UnicodeToEbcdic</var> and <var>AsciiToEbcdic</var>), however, have a parameter (as		their counterparts <var>UnicodeToEbcdic</var> and <var>AsciiToEbcdic</var>), however, have a parameter (as
	of <var class="product">Sirius Mods</var> version 7.6) that lets you decode or encode untranslatable characters.		of <var class="product">Sirius Mods</var> version 7.6) that lets you decode or encode untranslatable characters. </p>

	==Intrinsic method syntax: special cases==		==Intrinsic method syntax: special cases==

Dme at 14:05, 1 March 2014

2014-03-01T14:05:45Z

Show changes

JAL at 22:03, 14 October 2013

2013-10-14T22:03:09Z

← Older revision		Revision as of 22:03, 14 October 2013
Line 1:		Line 1:
	~~See also~~:		You may want to go directly to:
	*[[List of Float methods]]		*[[List of Float methods]]
	*[[List of String methods]]		*[[List of String methods]]

JAL: /* See also */

2013-10-14T22:02:02Z

JALWiccan: Automatically generated page update

2013-10-14T20:05:24Z

Automatically generated page update

← Older revision		Revision as of 20:05, 14 October 2013
Line 437:		Line 437:
	[[Category:System classes]]		[[Category:System classes]]
	[[Category:Overviews]]		[[Category:Overviews]]
	[[Category:~~Janus SOAP ULI~~ topics]]		[[Category:SOUL object-oriented programming topics]]

JALWiccan: Automatically generated page update

2013-06-03T21:29:03Z

Automatically generated page update

← Older revision		Revision as of 22:02, 14 October 2013
Line 432:		Line 432:
	==See also==		==See also==
	<ul>		<ul>
	<li>[[~~Janus SOAP ULI essentials~~]]		<li>[[Object oriented programming in SOUL]]
	</ul>		</ul>

← Older revision		Revision as of 21:29, 3 June 2013
Line 6:		Line 6:

	===Definition of Intrinsic classes===		===Definition of Intrinsic classes===
	In ~~“pure”~~ [http://en.wikipedia.org/wiki/Object-oriented_programming object-oriented languages], all datatypes are objects, that is, all datatypes are		In “pure” [http://en.wikipedia.org/wiki/Object-oriented_programming object-oriented languages], all datatypes are objects, that is, all datatypes are
	extension classes of some base object class. This means that even things that one		extension classes of some base object class. This means that even things that one
	might not immediately think of as objects, such as character strings or numbers, are, in		might not immediately think of as objects, such as character strings or numbers, are, in
Line 17:		Line 17:
	*They are syntactically identical to other objects. That is, the syntax for manipulating strings or numbers is the same as the syntax for manipulating other objects. More specifically, methods are applied to strings or numbers using the exact same syntax as when methods are applied to other objects.		*They are syntactically identical to other objects. That is, the syntax for manipulating strings or numbers is the same as the syntax for manipulating other objects. More specifically, methods are applied to strings or numbers using the exact same syntax as when methods are applied to other objects.
	Since the first aspect is concerned with the internal management of strings or numbers,		Since the first aspect is concerned with the internal management of strings or numbers,
	it is largely irrelevant from the perspective of a programmer using a ~~“pure”~~ object-		it is largely irrelevant from the perspective of a programmer using a “pure” object-
	oriented language. In fact, many languages that profess to be ~~“pure”~~ actually ~~“cheat~~,”		oriented language. In fact, many languages that profess to be “pure” actually “cheat,”
	internally, and they special-case string and numeric data. They do so because string		internally, and they special-case string and numeric data. They do so because string
	and numeric data is so important, and so heavily used in all programming languages,		and numeric data is so important, and so heavily used in all programming languages,
Line 34:		Line 34:
	would be less efficient than taking the number in <code>%y</code>, adding 13 to it, and setting <code>%x</code> to		would be less efficient than taking the number in <code>%y</code>, adding 13 to it, and setting <code>%x</code> to
	the result. Fortunately, the way this is actually done is purely an under-the-covers		the result. Fortunately, the way this is actually done is purely an under-the-covers
	implementation issue, so one can always pretend that ~~“pure”~~ object-oriented processing		implementation issue, so one can always pretend that “pure” object-oriented processing
	is being used.		is being used.
	This is so because numbers and strings are an example of a special class of objects		This is so because numbers and strings are an example of a special class of objects
Line 75:		Line 75:
	<p class="code">%myCount = %myCount + 23 </p>		<p class="code">%myCount = %myCount + 23 </p>

	Absence of methods that modify a value is what make a class immutable, and in ~~“pure”~~		Absence of methods that modify a value is what make a class immutable, and in “pure”
	object-oriented languages, basic string and numeric datatypes are always immutable.		object-oriented languages, basic string and numeric datatypes are always immutable.

Line 108:		Line 108:

	<ul>		<ul>
	<li>It allows <var class="product">User Language</var> to be used as a ~~“pure”~~ object-oriented language. This might be especially appealing to programmers who were trained in a pure object-oriented language.		<li>It allows <var class="product">User Language</var> to be used as a “pure” object-oriented language. This might be especially appealing to programmers who were trained in a pure object-oriented language.

	<li>It provides the benefit that expressions can generally be read in the natural left-to-right manner rather than the inside-to-outside manner required to understand an expression coded with $functions.		<li>It provides the benefit that expressions can generally be read in the natural left-to-right manner rather than the inside-to-outside manner required to understand an expression coded with $functions.
Line 125:		Line 125:
	datatypes in <var class="product">User Language</var>: string and numeric. In <var class="product">User Language</var> one can easily		datatypes in <var class="product">User Language</var>: string and numeric. In <var class="product">User Language</var> one can easily
	assign values from one datatype to another, even between numeric and string types.		assign values from one datatype to another, even between numeric and string types.
	This is intuitive and useful. Typically, in the ~~“real world”~~ one doesn't distinguish between		This is intuitive and useful. Typically, in the “real world” one doesn't distinguish between
	the string representation of a number and its numeric value used for calculation.		the string representation of a number and its numeric value used for calculation.
	Similarly, except for performance purposes and, perhaps, value limits, one is typically		Similarly, except for performance purposes and, perhaps, value limits, one is typically
	not concerned about how a value is stored internally.		not concerned about how a value is stored internally.

	This is not the case in some ~~“pure”~~ object-oriented languages where the paradigm of		This is not the case in some “pure” object-oriented languages where the paradigm of
	strong-datatyping is extended to numeric and string datatypes. This means that if one		strong-datatyping is extended to numeric and string datatypes. This means that if one
	wants to display the value of a numeric variable, one must explicitly convert it to a string		wants to display the value of a numeric variable, one must explicitly convert it to a string
Line 240:		Line 240:
	</p>		</p>

	==Automatic ~~“implicit”~~ conversion of intrinsic values==		==Automatic “implicit” conversion of intrinsic values==
	As with other methods, the colon that separates the intrinsic method object from the method		As with other methods, the colon that separates the intrinsic method object from the method
	name can be optionally preceded or followed by spaces. This could be done to enhance		name can be optionally preceded or followed by spaces. This could be done to enhance
Line 432:		Line 432:
	==See also==		==See also==
	<ul>		<ul>
	<li>[[Janus SOAP essentials]]		<li>[[Janus SOAP ULI essentials]]
	</ul>		</ul>