Re: [Pharo-users] Just curious...

Hi Richard For “Print it” representations of objects, you can browser the #printOn: method of the class of that object. For ScaledDecimal, it is: printOn: aStream "Append an approximated representation of the receiver on aStream. Use prescribed number of digits after decimal point (t

Re: [Pharo-users] sqlite garage

Must have missed the memo Thanks. I'll check it out! -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Just curious...

Errata: > E.g. If you write 0.1s3 it means you instantiate a ScaledDecimal that is 0.001 I meant: 0.1s3 = 0.100 Esteban A. Maringolo On Thu, Jan 30, 2020 at 2:28 PM Esteban Maringolo wrote: > > The number after the s is the scale of the ScaledDecimal. > > E.g. If you write 0.1s3 it means you

Re: [Pharo-users] [ANN] Hashtable on pharo-contributions

--- Begin Message --- Cool! If that helps, I'm currently working on a "custom" type of collection used for sampling objects based on probabilities. Should be ready in a few days if anyone's interested. For lack of a better word, it's currently called "SamplingSet". To make a long story short,

Re: [Pharo-users] Just curious...

The number after the s is the scale of the ScaledDecimal. E.g. If you write 0.1s3 it means you instantiate a ScaledDecimal that is 0.001 So it sems that printOn: in ScaledDecimal is being "explicit" as it prints 1 when other dialects don't. Regards, Esteban A. Maringolo On Thu, Jan 30, 2020 a

Re: [Pharo-users] sqlite garage

--- Begin Message --- Hi Jeff, If you haven't switched, the current SQLite repository that we would like to consider the "official" on is at https://github.com/pharo-rdbms/Pharo-SQLite3 Garage is being put on a weight loss program. > On Jan 29, 20

[Pharo-users] Just curious...

In the Playground, if I type in 0.1s and then "Print it", I get the following output: *0.1s1* What does the *s1* stand for? Why doesn't it simply print *s*?

[Pharo-users] [ANN] Hashtable on pharo-contributions

Hi! In Moose there is a project call "Hashtable". The goal of this project is to provide faster collections when they have a big number of elements. I think this is something that can be useful for more than just Moose so I extracted it to pharo-contributions so that we can use it and improve it

Re: [Pharo-users] Large Image Generator

--- Begin Message --- Thanks for your quick & detailed answer Pablo! I have a big list of ideas, all I need to do now is to type my notes! I wasn't sure if you wanted to test performance of a specific part/aspect of Pharo/VM hence my question to clarify all that! Is there any preferred image