Re: [Pharo-dev] [Glass] Floats problem with SIXX between Pharo and GemStone
On Wed, Feb 26, 2014 at 7:25 PM, Martin McClure < martin.mcclure@gemtalksystems.com> wrote:
On 02/26/2014 01:38 PM, Mariano Martinez Peck wrote:
So, of course " Float readFrom: '1.0000000000000000E-02' " -> 1.0
This is because Pharo only accepts lower-case letters for exponent ($e $d $q). So if you replace E with e Pharo will parse it as you wish.
Thanks all. I took this solution as the simples workaround. I overriden this method in my Pharo image: SqNumberPasrser>>exponentLetters "current comment" ^'edqEDQ' Now...a similar question is....is there a way to move Floats between Pharo and GemStone with SIXX *without *loosing decimals (no rounded)? Sixx in Pharo exports Floats doing #printString. So for example: 5645.0000000000000000000000000786786 printString -> '5645.0' I loose info. So what is the alternative? Thanks, -- Mariano http://marianopeck.wordpress.com
2014-03-03 16:14 GMT+01:00 Mariano Martinez Peck <marianopeck@gmail.com>:
On Wed, Feb 26, 2014 at 7:25 PM, Martin McClure < martin.mcclure@gemtalksystems.com> wrote:
On 02/26/2014 01:38 PM, Mariano Martinez Peck wrote:
So, of course " Float readFrom: '1.0000000000000000E-02' " -> 1.0
This is because Pharo only accepts lower-case letters for exponent ($e $d $q). So if you replace E with e Pharo will parse it as you wish.
Thanks all. I took this solution as the simples workaround. I overriden this method in my Pharo image:
SqNumberPasrser>>exponentLetters "current comment" ^'edqEDQ'
Now...a similar question is....is there a way to move Floats between Pharo and GemStone with SIXX *without *loosing decimals (no rounded)? Sixx in Pharo exports Floats doing #printString. So for example:
It depends how well Gemstone print/parse Floats...
5645.0000000000000000000000000786786 printString -> '5645.0'
Please provide a better case, because here: 5645.0000000000000000000000000786786 = 5645 So you don't loose anything... You might want to try with 0.5 successor or something like that... Note that Pharo 3.0 introduced a FloatPrintPolicy. If your default is inexact, then you might want to FloatPrintPolicy value: ExactFloatPrintPolicy new during: [ "Code to store in Sixx goes here..." ]. Nicolas I loose info. So what is the alternative?
Thanks,
-- Mariano http://marianopeck.wordpress.com
participants (2)
-
Mariano Martinez Peck -
Nicolas Cellier