[Pharo-project] Floats broken in latest image?
Hi guys! In latest pharo 2.0 (Latest update: #20150). I make Float initialize and it raises an exception. It seems that MaxVal := 1.7976931348623157e308. gets evaluated to 0.0 If I take Latest update: #20143, same vm, it works. Any idea what happened in the middle? :S Guille
that works properly in my image (20150 as well)... On 2012-06-21, at 18:32, Guillermo Polito wrote:
Hi guys!
In latest pharo 2.0 (Latest update: #20150). I make Float initialize and it raises an exception. It seems that
MaxVal := 1.7976931348623157e308.
gets evaluated to 0.0
If I take Latest update: #20143, same vm, it works.
Any idea what happened in the middle? :S
Guille
What happens when you inspect 3.14159265358979323846264338327950288 in a workspace? On Thu, Jun 21, 2012 at 6:48 PM, Camillo Bruni <camillobruni@gmail.com>wrote:
that works properly in my image (20150 as well)...
On 2012-06-21, at 18:32, Guillermo Polito wrote:
Hi guys!
In latest pharo 2.0 (Latest update: #20150). I make Float initialize and it raises an exception. It seems that
MaxVal := 1.7976931348623157e308.
gets evaluated to 0.0
If I take Latest update: #20143, same vm, it works.
Any idea what happened in the middle? :S
Guille
Ok, it seems I had not the right vm setup... I do not know which vm was my osx choosing. :/. But false alarm it seems... sorry :) On Thu, Jun 21, 2012 at 6:58 PM, Guillermo Polito <guillermopolito@gmail.com
wrote:
What happens when you inspect 3.14159265358979323846264338327950288 in a workspace?
On Thu, Jun 21, 2012 at 6:48 PM, Camillo Bruni <camillobruni@gmail.com>wrote:
that works properly in my image (20150 as well)...
On 2012-06-21, at 18:32, Guillermo Polito wrote:
Hi guys!
In latest pharo 2.0 (Latest update: #20150). I make Float initialize and it raises an exception. It seems that
MaxVal := 1.7976931348623157e308.
gets evaluated to 0.0
If I take Latest update: #20143, same vm, it works.
Any idea what happened in the middle? :S
Guille
Guillermo Polito wrote
I do not know which vm was my osx choosing. :/.
Yes, I've gone crazy with OS X choosing a different VM than I think, even after setting "Open with:"->"Change All...". Hasn't happened in a while, maybe fixed in Lion? Sean -- View this message in context: http://forum.world.st/Floats-broken-in-latest-image-tp4635963p4635994.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On 2012-06-21, at 19:19, Sean P. DeNigris wrote:
Guillermo Polito wrote
I do not know which vm was my osx choosing. :/.
Yes, I've gone crazy with OS X choosing a different VM than I think, even after setting "Open with:"->"Change All...". Hasn't happened in a while, maybe fixed in Lion?
nope, that still keeps on being a mistery. plus with the new FS the resources forks (or how they're called) are not properly set anymore :P I will have to fix that tomorrow at our micro sprint
On Thu, Jun 21, 2012 at 7:19 PM, Sean P. DeNigris <sean@clipperadams.com>wrote:
Guillermo Polito wrote
I do not know which vm was my osx choosing. :/.
Yes, I've gone crazy with OS X choosing a different VM than I think, even after setting "Open with:"->"Change All...".
I suffer the same problem. Even doing that, the OSX would chose a different VM sometimes.... :(
Hasn't happened in a while, maybe fixed in Lion?
Sean
-- View this message in context: http://forum.world.st/Floats-broken-in-latest-image-tp4635963p4635994.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Mariano http://marianopeck.wordpress.com
Ok, this is happening when I load a package of my own... So, I'll see deeper... On Thu, Jun 21, 2012 at 6:32 PM, Guillermo Polito <guillermopolito@gmail.com
wrote:
Hi guys!
In latest pharo 2.0 (Latest update: #20150). I make Float initialize and it raises an exception. It seems that
MaxVal := 1.7976931348623157e308.
gets evaluated to 0.0
If I take Latest update: #20143, same vm, it works.
Any idea what happened in the middle? :S
Guille
participants (4)
-
Camillo Bruni -
Guillermo Polito -
Mariano Martinez Peck -
Sean P. DeNigris