Float(string) and similar functions need a better translation

[vinivendra]

The current translation of Float(string) turns it into string.toFloat(). This can be a problem when the translations fail: the Swift version returns nil and the Kotlin version throws an error.

This problem seems to be similar to that in #2.

A way to solve both these problems (and possibly more to come) is to add something like this to the GryphonKotlinLibrary:

fun <T> tryOrNull(autoclosure: () -> T): T? {
	try {
		return autoclosure()
	}
	catch (exception: Exception) {
		return null
	}
}

fun <T> T.nullIf(value: T): T? {
	if (this == value) {
		return null
	}
	else {
		return this
	}
}

fun main(args: Array<String>) {
	val a: Float? = tryOrNull { "abc".toFloat() } // null
	val b: Float? = tryOrNull { "0".toFloat() } // 0.0f

	val c: Int? = (-1).nullIf(-1) // null
	val d: Int? = (3).nullIf(-1) // 3
}

It might seem unintuitive to users at first, but it might be better than creating several individual functions to fix each of these problems.

[vinivendra]

Once this is done, it might be interesting to add a direct translation for Float(string)! etc.

[rlinoz]

Kotlin has a string.toFloatOrNull()

One approach could be to always use the to<NumberType>OrNull() function instead