Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

Hi Phil, On Thu, Nov 10, 2016 at 2:19 AM, p...@highoctane.be wrote: > > > On Thu, Nov 10, 2016 at 10:31 AM, Denis Kudriashov > wrote: > >> >> 2016-11-10 9:49 GMT+01:00 p...@highoctane.be : >> >>> Ah, but then it may be more

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

On Thu, Nov 10, 2016 at 1:31 AM, Denis Kudriashov wrote: > > 2016-11-10 9:49 GMT+01:00 p...@highoctane.be : > >> Ah, but then it may be more interesting to have a data image (maybe a lot >> of these) and a front end image. >> >> Isn't Seamless something

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

Le 14/11/2016 à 21:51, stepharo a écrit : Hi thierry did you happen to have a techreport or any description of your work? It's a chapter in my PhD thesis ;) Thierry Stef Le 11/11/16 à 11:44, Thierry Goubier a écrit : Le 11/11/2016 à 11:29, Stephan Eggermont a écrit : On 10/11/16

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

Hi thierry did you happen to have a techreport or any description of your work? Stef Le 11/11/16 à 11:44, Thierry Goubier a écrit : Le 11/11/2016 à 11:29, Stephan Eggermont a écrit : On 10/11/16 21:35, Igor Stasenko wrote: No, no, no! This is simply not true. It is you, who writes the

Re: [Pharo-dev] macOS Sierra support

Good Tx Le 14/11/16 à 11:36, Esteban Lorenzano a écrit : for the moment, I added this nice (?) alert when you press mac download button: On 14 Nov 2016, at 11:30, Esteban Lorenzano > wrote: On 14 Nov 2016, at 11:01, MartinW

[Pharo-dev] [ANN] WKHTML2PDF converted to UFFI

Hi, WKHTML2PDF was broken in recent Pharo version as my original version of the project was based on NativeBoost and we now meanwhile switched to UFFI with Pharo to provide a unified foreign function interface. Long story short: I now found the time to update the project to use UFFI and make

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

I was hit by this today already as it made Catalog slow like hell (which I fixed): https://pharo.fogbugz.com/f/cases/19342/. +1 for the short-term revert +10 for aligning Squeak and Pharo with a more intention revealing name Thx T. > Gesendet: Montag, 14. November 2016 um 19:49 Uhr > Von:

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Here is the CI thing for Travis. https://github.com/hpi-swa/smalltalkCI Phil On Mon, Nov 14, 2016 at 7:15 PM, Cyril Ferlicot D. wrote: > Le 14/11/2016 à 18:12, Denis Kudriashov a écrit : > > > > But we already has fork of Metacello in image. Many Metacello packages

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Le 14/11/2016 à 18:12, Denis Kudriashov a écrit : > > But we already has fork of Metacello in image. Many Metacello packages > are from integrator. > So loading latest version is not possible now. And merge will not be > easy task anyway. > But maybe I am wrong here. For some projects as

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

> On 14 Nov 2016, at 18:12, Denis Kudriashov wrote: > > > 2016-11-14 17:18 GMT+01:00 Cyril Ferlicot D. >: > > Why? ConfigurationOf~ not collect any pragmas by themselves. They only > > declare versions by

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

2016-11-14 17:18 GMT+01:00 Cyril Ferlicot D. : > > Why? ConfigurationOf~ not collect any pragmas by themselves. They only > > declare versions by pragmas. > > And we only need to fix Pharo version of Metacello which is already fork. > > Changes to Metacello should be

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

> On 14 Nov 2016, at 17:18, Cyril Ferlicot D. wrote: > > On 14/11/2016 15:50, Denis Kudriashov wrote: >> >> 2016-11-14 15:37 GMT+01:00 Esteban A. Maringolo > >: >> >>Breaking Metacello in any version = Not good.

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

> On 14 Nov 2016, at 17:18, Cyril Ferlicot D. wrote: > > On 14/11/2016 15:50, Denis Kudriashov wrote: >> >> 2016-11-14 15:37 GMT+01:00 Esteban A. Maringolo > >: >> >>Breaking Metacello in any version = Not good.

Re: [Pharo-dev] Performance difference between Pharo 32bits and 64bits

Hi Eliot, 2016-11-14 16:57 GMT+01:00 Eliot Miranda : > Hi Thierry, > > > > On Nov 14, 2016, at 7:04 AM, Thierry Goubier > wrote: > > > > Has anybody seen performance differences between the 32bits and the > 64bits versions of Pharo 6 ? > > > >

[Pharo-dev] Saving and retrieving global settings

Hi, I added some settings into Iceberg and stored them. I expected that they would be automatically loaded into a new image, but it does not work. What I understand is that settings are loaded when the image is opened for the first time, and Iceberg isn't there yet. Then I load Iceberg but it will

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

On 14/11/2016 15:50, Denis Kudriashov wrote: > > 2016-11-14 15:37 GMT+01:00 Esteban A. Maringolo >: > > Breaking Metacello in any version = Not good. > > Metacello is very backward compatible but breaking pragma semantics > would

Re: [Pharo-dev] Performance difference between Pharo 32bits and 64bits

Hi Thierry, > On Nov 14, 2016, at 7:04 AM, Thierry Goubier > wrote: > > Has anybody seen performance differences between the 32bits and the 64bits > versions of Pharo 6 ? > > I'm seeing a speedup greater than 2 on some intensive numerical code. > > Note that, on

Re: [Pharo-dev] Performance difference between Pharo 32bits and 64bits

2016-11-14 16:24 GMT+01:00 Clément Bera : > Hi Thierry, > > On the speed center you can compare 32 bits and 64 bits linux VMs: > http://squeak.org/codespeed/ > > Interesting to see the rsqueak results on that type of benchs. Mandelbrot would be the closest. > > Normally

Re: [Pharo-dev] Performance difference between Pharo 32bits and 64bits

Hi Thierry, On the speed center you can compare 32 bits and 64 bits linux VMs: http://squeak.org/codespeed/ Normally Pharo 64 should be overall slightly slower than Pharo 32 because 70% of the memory is used for pointers, implying twice more data to process by the processor for pointer

Re: [Pharo-dev] #printShowingMaxDecimalPlaces: What do you think?

I vote for the NumberFormatter. It adds another layer, which can be a pain, but gives you much more flexibility. Plus it decouples the formatting from all of the number classes. VA Smalltalk has something like this. Brad Selfridge 913-269-2385 > On Nov 14, 2016, at 8:38 AM, Sven Van

[Pharo-dev] Performance difference between Pharo 32bits and 64bits

Has anybody seen performance differences between the 32bits and the 64bits versions of Pharo 6 ? I'm seeing a speedup greater than 2 on some intensive numerical code. Note that, on that code, Pharo 64bits is slower than R, by around 30%. The code overall is memory bound. Thierry

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

2016-11-14 11:50 GMT-03:00 Denis Kudriashov : > > 2016-11-14 15:37 GMT+01:00 Esteban A. Maringolo : >> >> Breaking Metacello in any version = Not good. >> >> Metacello is very backward compatible but breaking pragma semantics >> would require a rewrite

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

2016-11-14 15:37 GMT+01:00 Esteban A. Maringolo : > Breaking Metacello in any version = Not good. > > Metacello is very backward compatible but breaking pragma semantics > would require a rewrite of many configurations that work okay today > Why? ConfigurationOf~ not

Re: [Pharo-dev] #printShowingMaxDecimalPlaces: What do you think?

I am voting against because both methods are very similar while we are trying to clean. Also, if I would have to present a number I would personally always prefer the .00 for uniformity. But I understand what you want. I think a NumberFormatter object would be better -- what about thousands

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

2016-11-14 11:27 GMT-03:00 p...@highoctane.be : > Breaking Metacello in Pharo 6: Not good. Revert: +1 Breaking Metacello in any version = Not good. Metacello is very backward compatible but breaking pragma semantics would require a rewrite of many configurations that work

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Breaking Metacello in Pharo 6: Not good. Revert: +1 On Mon, Nov 14, 2016 at 2:16 PM, Esteban Lorenzano wrote: > we need to revert. > this is a huge mess in a very inappropriate moment :) > > Esteban > > > On 14 Nov 2016, at 13:56, Tudor Girba wrote: >

Re: [Pharo-dev] macOS Sierra support

If I try to start the Pharo from the Download page e.g. from my Desktop I get the following information: - Pharo cannot write to the changes file named

[Pharo-dev] #printShowingMaxDecimalPlaces: What do you think?

Hi! I have a problem in an application, I need to print some numbers with 2 decimals max. The numbers can be an Integer, Float or Fraction. I checked and found Number>>#printShowingDecimalPlaces:. This is cool but this is not what I want because when I get "10", I want to print "10" and not

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

We should not revert whole update so I created an issue: https://pharo.fogbugz.com/f/cases/19338/Revert-18233-improving-Pragma-API -- Pavel 2016-11-14 14:30 GMT+01:00 Tudor Girba : > Agreed. So who is doing it? > > Doru > > > > On Nov 14, 2016, at 2:16 PM, Esteban

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Agreed. So who is doing it? Doru > On Nov 14, 2016, at 2:16 PM, Esteban Lorenzano wrote: > > we need to revert. > this is a huge mess in a very inappropriate moment :) > > Esteban > >> On 14 Nov 2016, at 13:56, Tudor Girba wrote: >> >> Hi, >>

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

we need to revert. this is a huge mess in a very inappropriate moment :) Esteban > On 14 Nov 2016, at 13:56, Tudor Girba wrote: > > Hi, > > Indeed, I forgot that #selector is doing something else. This is a bit of a > mess. Either we revert it today, or we leave it.

Re: [Pharo-dev] macOS Sierra support

done > On 14 Nov 2016, at 13:46, Tudor Girba wrote: > > Hi, > > Looks good. I would only add explicitly that we are talking about Apple’s > security policies. > > “… Due to changes in security policies of MacOS …” > > Cheers, > Doru > > >> On Nov 14, 2016, at 11:36

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Hi, Indeed, I forgot that #selector is doing something else. This is a bit of a mess. Either we revert it today, or we leave it. Otherwise, more projects will adopt the new API only to break again afterwards. Doru > On Nov 14, 2016, at 1:50 PM, Cyril Ferlicot D. >

[Pharo-dev] [pharo-project/pharo-core] 75a952: 60290

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 75a9520e8197d944ecb87843f77c9cec5030950b https://github.com/pharo-project/pharo-core/commit/75a9520e8197d944ecb87843f77c9cec5030950b Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60290 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

On 14/11/2016 13:44, Tudor Girba wrote: > Hi, > > Please do not revert the API. Just comment out the deprecation. The code in > Moose was already updated to the new API and I presume other projects might > be in the same situation. > > Cheers, > Doru > > > -- > www.tudorgirba.com >

Re: [Pharo-dev] macOS Sierra support

Hi, Looks good. I would only add explicitly that we are talking about Apple’s security policies. “… Due to changes in security policies of MacOS …” Cheers, Doru > On Nov 14, 2016, at 11:36 AM, Esteban Lorenzano wrote: > > for the moment, I added this nice (?) alert

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Hi, Please do not revert the API. Just comment out the deprecation. The code in Moose was already updated to the new API and I presume other projects might be in the same situation. Cheers, Doru > On Nov 14, 2016, at 10:00 AM, Pavel Krivanek wrote: > > Revert the

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Great. Le 14 nov. 2016 11:23, "Esteban Lorenzano" a écrit : > > On 14 Nov 2016, at 10:00, Pavel Krivanek wrote: > > Revert the new API. It was mistake to integrate it in the code freeze > phase. > > > yep, that’s accurate :) > > Esteban > > > --

Re: [Pharo-dev] macOS Sierra support

This is weird but I have never experienced this "sandbox" thing I have Sierra, updated to the latest and when I download this zip to my downloads folder, I uncompress it and double click the application without moving to the application folder it works without doing anything additionally or

Re: [Pharo-dev] macOS Sierra support

for the moment, I added this nice (?) alert when you press mac download button: > On 14 Nov 2016, at 11:30, Esteban Lorenzano wrote: > > >> On 14 Nov 2016, at 11:01, MartinW wrote: >> >> Can someone put a note to the website

Re: [Pharo-dev] macOS Sierra support

> On 14 Nov 2016, at 11:01, MartinW wrote: > > Can someone put a note to the website (http://pharo.org/download)? It is > frustrating for users to follow the link to > http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a > defunct Pharo installation. no, in

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

> On 14 Nov 2016, at 10:00, Pavel Krivanek wrote: > > Revert the new API. It was mistake to integrate it in the code freeze phase. yep, that’s accurate :) Esteban > > -- Pavel > > 2016-11-14 9:53 GMT+01:00 Nicolai Hess

Re: [Pharo-dev] macOS Sierra support

Can someone put a note to the website (http://pharo.org/download)? It is frustrating for users to follow the link to http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a defunct Pharo installation. Sean P. DeNigris wrote > > EstebanLM wrote >> the regular download by zeroconf

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Revert the new API. It was mistake to integrate it in the code freeze phase. -- Pavel 2016-11-14 9:53 GMT+01:00 Nicolai Hess : > > > 2016-11-14 9:42 GMT+01:00 Pavel Krivanek : > >> Well, we will revert the change >> >> > revert the

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

2016-11-14 9:42 GMT+01:00 Pavel Krivanek : > Well, we will revert the change > > revert the autodeprecation or the new api ? I made a fix for case 19336 Finder and FileList can now work with the new api. > -- Pavel > > 2016-11-13 17:33 GMT+01:00 Nicolai Hess

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

Well, we will revert the change -- Pavel 2016-11-13 17:33 GMT+01:00 Nicolai Hess : > > > 2016-11-13 10:06 GMT+01:00 Nicolai Hess : > >> >> >> 2016-11-11 10:55 GMT+01:00 Pavel Krivanek : >> >>> Hi, >>> >>> the API of Pragma