JavaScript global methods can be used on all JavaScript data types.

• Number ( )
• parseFloat ( )
• parseInt ( )

Number ( )

The Number() function converts the object argument to a number that
represents the object’s value.
If the value cannot be converted to a legal number, NaN is returned.
If the parameter is a Date object, the Number() function returns the number of
milliseconds since midnight January 1, 1970, UTC.

Ex: –

Number(true)
Number(“100”)
Number(100/“Hello”)

parseInt ( )

The parseInt() function parses a string and returns an integer.

Syntax:- parseInt(string, radix)

The radix parameter is used to specify which numeral system to be used, for example, a
the radix of 16 (hexadecimal) indicates that the number in the string should be parsed from
a hexadecimal number to a decimal number.

If the radix parameter is omitted, JavaScript assumes the following:

• If the string begins with “0x”, the radix is 16 (hexadecimal)
• If the string begins with any other value, the radix is 10 (decimal)

Only the first number in the string is returned.
Leading and trailing spaces are allowed.
If the first character cannot be converted to a number, parseInt() returns NaN.

parseInt ( )

parseFloat ( )

The parseFloat() function parses a string and returns a floating-point number. This function determines if the first character in the specified string is a number. If it is, it parses the string until it reaches the end of the number, and returns the number as a number, not as a string.

Syntax: – parseFloat(string)

• Only the first number in the string is returned!
• Leading and trailing spaces are allowed.
• If the first character cannot be converted to a number, parseFloat() returns NaN.

parseFloat ( )

The post Global JavaScript Methods appeared first on scmGalaxy.

How Perforce change list number works?

Perforce assigns numbers to changelists and also maintains a default changelist, which is numbered when you submit it. You can create multiple changelists to organize your work. For example, one changelist might contain files that are changed to implement a new feature, and another changelist might contain a bug fix. Changelists are renumbered so that submitted changelist numbers always ascend in chronological order.

Pending numbered changelists might be renumbered when they are submitted to ensure that submitted changelist numbers are always ascending in chronological order. For example, if changelist A is submitted before changelist B, then changelist B’s number will be higher when it is submitted.

Perforce change list numbers are serial. Once a CL number has been assigned via a submit, only the next number in series will be used.

One way this could happen is that you had pending work in CL 326042 and something in your default and the latest submitted CL is 326041.

Reference

http://www.perforce.com/perforce/doc.current/manuals/p4guide/04_files.html
http://kb.perforce.com/article/781/changelist-renumbered-on-submit

The post How Perforce changelist number works? | Perforce Guide appeared first on scmGalaxy.