Int keyword - Revision history

Sunjammer: Added links

2020-04-13T13:33:13Z

Added links

2011-08-15T11:22:55Z

Updating links

2011-08-02T22:37:54Z

2011-08-02T22:28:03Z

Fixing category

2011-08-02T22:21:38Z

2009-08-01T04:30:08Z

2009-08-01T03:57:33Z

‎Persistence

2009-07-30T23:17:34Z

2009-07-30T18:33:14Z

2009-07-30T18:32:23Z

@@ Line 45: / Line 45: @@
 == Special ==
-In [[dascript]] there is no Boolean type.  Instead integer values are used to represent Boolean values: 0 represents the '''false''' state and anything else represents the '''true''' state.  For convenience two int constants have been defined in script.ldf to represent the true and false states:
+In [[dascript]] there is no Boolean type.  Instead integer values are used to represent Boolean values: 0 represents the '''false''' state and anything else represents the '''true''' state.  For convenience two [[boolean constants]] have been defined in [[script.ldf]] to represent the true and false states:
 <dascript>

@@ Line 4: / Line 4: @@
 == Literals ==
-A literal is a textual representation of a particular value of a type.
+An int [[Scripting terminology#literal|literal]] can be a decimal (base 10) or hexadecimal (base 16) number. A decimal integer literal consists of a string of decimal digits (0-9). A hexadecimal literal consists of "0x" or "0X" followed by a string of hexadecimal digits (0-9, a-f, A-F).
-−
 An int literal can be decimal (base 10) or hexadecimal (base 16). A decimal integer literal consists of a string of decimal digits (0-9). A hexadecimal literal consists of "0x" or "0X" followed by a string of hexadecimal digits (0-9, a-f, A-F).
 == Conversion ==

← Older revision		Revision as of 22:37, 2 August 2011
Line 80:		Line 80:


−	[[Category:~~Scripting keywords~~]]	+	[[Category:Keywords]]

← Older revision		Revision as of 22:28, 2 August 2011
Line 80:		Line 80:


−	[[Category: ~~DAScript types~~]]	+	[[Category:Scripting keywords]]

@@ Line 33: / Line 33: @@
 == Persistence ==
-The following functions allow an int to exist outside of the scope of the current script by storing it on an object, effect or event:
+The following functions allow an int to exists outside of the scope of the current script by storing it on an object, effect or event:
 * [[SetLocalInt]]

← Older revision	Revision as of 22:21, 2 August 2011
(No difference)

@@ Line 34: / Line 34: @@
 The following functions allow an int to exist outside of the scope of the current script by storing it on an object, effect or event:
 * [[GetLocalInt]]
@@ Line 39: / Line 45: @@
 * [[GetEventInteger]]
 == Special ==

@@ Line 1: / Line 1: @@
 __NOTOC__
-The '''int''' type is a signed 32-bit integer between -2,147,483,648 and 2,147,483,647.  The default value is 0.
+The '''int''' type represents a signed 32-bit integer between -2,147,483,648 and 2,147,483,647.  The default value is 0.
 == Literals ==
@@ Line 33: / Line 33: @@
 == Persistence ==
-The following functions allow an int to exist outside of the scope of the current script by storing it on an object, event or effect:
+The following functions allow an int to exist outside of the scope of the current script by storing it on an object, effect or event:
 * [[GetLocalInt]]
 * [[GetEffectInteger]]
-The following functions allow an int which exist outside of the scope of the current script to be used in the current script by retrieving it from an object, event or effect:
+The following functions allow an int which exist outside of the scope of the current script to be used in the current script by retrieving it from an object, effect or event:
 * [[SetLocalInt]]
 * [[SetEffectInteger]]
 == Special ==
@@ Line 53: / Line 53: @@
      int TRUE = 1;
 </dascript>
 == Examples ==

← Older revision	Revision as of 18:32, 30 July 2009
(No difference)