Talk:Proper Money Handling (JSON-RPC) - Revision history

Luke-jr at 00:57, 11 June 2011

2011-06-11T00:57:24Z

← Older revision		Revision as of 00:57, 11 June 2011
Line 4:		Line 4:
	And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.		And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.

	~~::The real solution is not to write money-handling code in ECMAScript. [[User:Sdfdsafsaff\|Sdfdsafsaff]] 23:15, 10 June 2011 (GMT)~~

	For Ruby I think the syntax is:		For Ruby I think the syntax is:
Line 15:		Line 14:

	Since the value is already in ECMAScript's native representation, why would you use a conversion function?		Since the value is already in ECMAScript's native representation, why would you use a conversion function?
			* The RPC value is passed as an inexact floating point. Money handling should always be done as integers. --[[User:Luke-jr\|Luke-jr]] 00:57, 11 June 2011 (GMT)

2011-06-10T23:15:16Z

← Older revision		Revision as of 23:15, 10 June 2011
Line 4:		Line 4:
	And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.		And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.

			::The real solution is not to write money-handling code in ECMAScript. [[User:Sdfdsafsaff\|Sdfdsafsaff]] 23:15, 10 June 2011 (GMT)

	For Ruby I think the syntax is:		For Ruby I think the syntax is:

2011-06-10T23:14:20Z

ECMAScript?: new section

← Older revision		Revision as of 23:14, 10 June 2011
Line 10:		Line 10:

	Correct?		Correct?

			== ECMAScript? ==

			Since the value is already in ECMAScript's native representation, why would you use a conversion function?

2011-06-04T22:54:15Z

2011-06-04T22:54:02Z

← Older revision		Revision as of 22:54, 4 June 2011
Line 3:		Line 3:

	And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.		And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.


			For Ruby I think the syntax is:

			=Ruby
			(f * 1e8).round.to_f / 1e8

			Correct?

2011-03-04T02:31:44Z

← Older revision		Revision as of 02:31, 4 March 2011
Line 1:		Line 1:
	RE: best practices in ECMAScript:		RE: best practices in ECMAScript:
	Just converting to base units doesn't magically fix the issues; if I have 1.0BTC == 100000000.0 base units and I need to divide that value into three equal pieces, I'm going to run into issues whether the result is 0.3333333.... or 3333333.33333...		Just converting to base units doesn't magically fix the issues; if I have 1.0BTC == 100000000.0 base units and I need to divide that value into three equal pieces, I'm going to run into issues whether the result is 0.3333333.... or 3333333.33333...

			And the fixes are the same: either round to the nearest .0000001 or to the nearest 1 before display, etc.

2011-03-04T02:29:40Z

← Older revision		Revision as of 02:29, 4 March 2011
Line 1:		Line 1:
	~~luke-jr~~: ~~what is your python code supposed~~ to ~~do???? Multiplying all ints by 10e8~~ is ~~a bad idea~~.		RE: best practices in ECMAScript:
			Just converting to base units doesn't magically fix the issues; if I have 1.0BTC == 100000000.0 base units and I need to divide that value into three equal pieces, I'm going to run into issues whether the result is 0.3333333.... or 3333333.33333...

2011-03-03T15:55:15Z

← Older revision		Revision as of 15:55, 3 March 2011
Line 1:		Line 1:
	luke-jr: what is your python code supposed to do????		luke-jr: what is your python code supposed to do???? Multiplying all ints by 10e8 is a bad idea.

2011-03-03T15:17:15Z

Created page with "luke-jr: what is your python code supposed to do????"

New page

luke-jr: what is your python code supposed to do????