Probable Lucee6 bug...
# lucee
a
Probable Lucee6 bug...
Copy code
<cfscript>
biOp1 = JavaCast("BigInteger", "1827121492050112345678181400")
biOp2 = JavaCast("BigInteger", "97")
writeDump([
	precisionEvaluate = [
		// CF can't run these as it only accepts integers for op1 for mod. Comment them out
		string = PrecisionEvaluate("1827121492050112345678181400" mod 97), // 34 on Lucee 5 & 6
		BigInt = PrecisionEvaluate(biOp1 mod 97) // Lucee 5: 34; Lucee 6: 68. 34 is correct.
	],
	BigInt = biOp1,
	mod = biOp1.mod(biOp2) // 34 on all
])
</cfscript>
Seems
precisionEvaluate
has changed when it's given a BigInt as op1 in this case This breaks our install process on Lucee6, so I can't even run our tests. I will check to see if I can work around it.
Ping @alexpixl8 / @zackster
a
I know there is a line item around changes to precise math, can you look under lucee 6 admin there is a reference to a setting switch from memory
I’m on mobile at mo but pretty sure there is some change there
And a setting switch ?
a
Found it. No difference.
Worth a punt though.
I think I can hack the install code to work around this though, so will try that and see if I can get to the point where it installs and I can run tests.
Or "Monday afternoon at the pub" as I like to think of it
@zackster this. I never raised a ticket though 😞