Re: [Pharo-dev] [Pharo-users] why is adding instance variables so slow?

Hi, with Yuriy and Miroslava we have tried to finish a pull request for conversion of rules to Renraku. But we had to face to a strange failing tests. It was not clear on the first sight but these tests were failing because of time-outs. Then we realized that the reason for this may be in big

Re: [Pharo-dev] Pharo and special unary selectors

From one perspective, full names are clearer at the cost of some typing 33 percent 45 dollar 100 kilometerPerHour 4 newtonMeter 200 bitsPerSecond And just like there is a limited namespace for class names (and prefixes to separate them), the namespace of selectors is global and limited too.

Re: [Pharo-dev] Pharo and special unary selectors

Well you would change the syntax of Pharo, which I don't think will be met with a lot of enthusiasm. How would you distinguish it from unary messages? How would you distinguish it from something that should trigger compilation error instead? ($ for characters) Also; 1 ml is one milliliter, or

[Pharo-dev] [Pharo 7.0-dev] Build #299: 20603-Integration-of-new-bytecode-set-Sista-V1-by-default-green-tests

There is a new Pharo build available! The status of the build #299 was: SUCCESS. The Pull Request #484 was integrated: "20603-Integration-of-new-bytecode-set-Sista-V1-by-default-green-tests" Pull request url: https://github.com/pharo-project/pharo/pull/484 Issue Url:

[Pharo-dev] Pharo Quality: raising the quality level in Pharo 7 and onwards

Hi, when we forked Pharo back in the days (2008) one of the primary goals of Pharo was and still is to provide a CLEAN SYSTEM. Now after nearly 10 years we have done already an amazing job. But we are still not there. While it is a good thing that we rewrite parts of the image, work on

Re: [Pharo-dev] Pharo and special unary selectors

> Well you would change the syntax of Pharo I'm not sure this is a syntax change like others. Haven yet thought about it too deeply. Where is the difference between an unary method #m and #% from the callers point of view? Either there is an argument object then % is a binary - if not it is an

[Pharo-dev] [Pharo 7.0-dev] Build #300: 20647-SortFunction-should-be-composable

There is a new Pharo build available! The status of the build #300 was: SUCCESS. The Pull Request #440 was integrated: "20647-SortFunction-should-be-composable" Pull request url: https://github.com/pharo-project/pharo/pull/440 Issue Url: https://pharo.fogbugz.com/f/cases/20647 Build

Re: [Pharo-dev] slow Pharo downloading and Travis

Performance has been fairly reasonable lately, until just now... from PharoLauncher I downloaded Pharo 7 latest-32 and that zipped along okay, then immediately downloaded Pharo 7 latest-64 and it crawled. About 30 seconds or more per 1%. That would have been ~16:50TZ+8) I went to dinner. After

Re: [Pharo-dev] Pharo Quality: raising the quality level in Pharo 7 and onwards

Ok. Now, how is one using those super tools? You mean Quality Assistant for example? Phil On Fri, Nov 17, 2017 at 11:52 AM, Torsten Bergmann wrote: > Hi, > > when we forked Pharo back in the days (2008) one of the primary goals of > Pharo was and still is to provide a CLEAN

Re: [Pharo-dev] undocumented method is quest of comment

https://github.com/pharo-project/pharo/pull/487 2017-11-16 23:32 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > It's not documented because hashing is complex... > The goal is to shuffle the receiver bits and distribute them over the > available 28bits used for hash codes. >

Re: [Pharo-dev] slow Pharo downloading and Travis

We are experimenting with a mirror that seems to work good. I mailed you some info privately. I am not sure if we can make this public already (Marcus ?) > On 17 Nov 2017, at 13:05, Ben Coman wrote: > > Performance has been fairly reasonable lately, until just now... >

[Pharo-dev] Pharo and special unary selectors

Hi, just something to think about: one thing I always liked about Smalltalk is that it allows for nice DSL's. We have nice things like a unit framework in Pharo, ... In the most simple case one can easily implement own units just by providing a unary messages: 1 m 1 second 1 px 1 EUR

Re: [Pharo-dev] [Pharo 7.0-dev] Build #299: 20603-Integration-of-new-bytecode-set-Sista-V1-by-default-green-tests

The title of this integration is misleading and Clement Bera clarified it in the Pull Request comments: Here is a copy of his comment: «Just to clarify. This slice makes all tests green which means the bytecode set is ready for integration, it does not integrate it. Integration of the new

Re: [Pharo-dev] Pharo Quality: raising the quality level in Pharo 7 and onwards

> nor how difficult it would be to automatically report why the contribution > was rejected > For this GitHub and Gitlab have hooks so other services can tell whether something is failing. See checks for example here https://github.com/hpi-swa/smalltalkCI/pull/311#partial-pull-merging (travis,

Re: [Pharo-dev] Dark Mode List

> On 17 Nov 2017, at 16:11, Stephane Ducasse wrote: > > I love your signature. > Now how should I interpret you email :) I like how Pharo looks in the Dark Theme. It is very cool. > On Fri, Nov 17, 2017 at 3:59 PM, Sven Van Caekenberghe wrote: >

Re: [Pharo-dev] [Pharo-users] why is adding instance variables so slow?

tx guys On Fri, Nov 17, 2017 at 10:59 AM, Pavel Krivanek wrote: > Hi, > > with Yuriy and Miroslava we have tried to finish a pull request for > conversion of rules to Renraku. But we had to face to a strange failing > tests. It was not clear on the first sight but these

Re: [Pharo-dev] undocumented method is quest of comment

Indeed no little action is worth a thousand words. Everybody plants its own seed. Tx nicolas and Pavel. Stef On Fri, Nov 17, 2017 at 3:00 PM, Nicolas Cellier wrote: > One little action is worth a thousand words :) > > > 2017-11-17 11:51 GMT+01:00 Pavel

Re: [Pharo-dev] Pharo Quality: raising the quality level in Pharo 7 and onwards

Hi torsten Thanks for raising this. I would like to add two points: - Comment methods with examples: This is why I introduced >>> look at at:at: I should fix flatCollect: btw To me this is super important to document even the classes that we all know. Because newcomers don't know.

Re: [Pharo-dev] Pharo Quality: raising the quality level in Pharo 7 and onwards

It seems to me that you could technically enforce with github/travis: - save the result of previous code critics - pass the code critics on travis - diff with previous - reject any contribution creating new critics I don't know how difficult it is to implement, nor how difficult it would be to

Re: [Pharo-dev] undocumented method is quest of comment

One little action is worth a thousand words :) 2017-11-17 11:51 GMT+01:00 Pavel Krivanek : > https://github.com/pharo-project/pharo/pull/487 > > 2017-11-16 23:32 GMT+01:00 Nicolas Cellier gmail.com>: > >> It's not documented because hashing

[Pharo-dev] [Pharo 7.0-dev] Build #303: 20711 Unused temps in RubTextEditor, RubParagraph, RubMethodEditingExample, ReflectiveMethod, RxMatcher

There is a new Pharo build available! The status of the build #303 was: SUCCESS. The Pull Request #494 was integrated: "20711 Unused temps in RubTextEditor, RubParagraph, RubMethodEditingExample, ReflectiveMethod, RxMatcher" Pull request url:

Re: [Pharo-dev] Dark Mode List

ahhh. :) I think that we should have nice white theme and a nice dark new theme for Pharo 70. Because we need to see the difference. Since Pharo 60 was dark by default Pharo 70 should be white by default so that the "others" people can argue :) Personally I used the default either white or dark.

[Pharo-dev] [Pharo 7.0-dev] Build #302: 20707 Unused temps in WindowsStore, WaitfreeQueue, VersionnerProjectPanel,

There is a new Pharo build available! The status of the build #302 was: SUCCESS. The Pull Request #490 was integrated: "20707 Unused temps in WindowsStore, WaitfreeQueue, VersionnerProjectPanel, " Pull request url: https://github.com/pharo-project/pharo/pull/490 Issue Url:

Re: [Pharo-dev] Pharo and special unary selectors

I would really like to see % removed as a binary selector and available to use in unary or keyword ones. The only implementor in a Pharo 6 image is: % aNumber ^ self \\ aNumber So it's juts aliasing \\ , and % most widespread usage in the real world is por percentages (the use in modular

Re: [Pharo-dev] Pharo and special unary selectors

2017-11-17 18:32 GMT+01:00 Thierry Goubier : > Le 17/11/2017 à 10:14, Nicolas Cellier a écrit : > >> >> >> 2017-11-17 17:40 GMT+01:00 Gabriel Cotelli g.cote...@gmail.com>>: >> >> I would really like to see % removed as a binary selector and >>

Re: [Pharo-dev] Pharo and special unary selectors

Le 17/11/2017 à 10:14, Nicolas Cellier a écrit : 2017-11-17 17:40 GMT+01:00 Gabriel Cotelli >: I would really like to see % removed as a binary selector and available to use in unary or keyword ones. The only implementor in a

Re: [Pharo-dev] Little Chapter on Hash methods

tx ALOT On Fri, Nov 17, 2017 at 7:04 PM, Sean P. DeNigris wrote: > Stephane Ducasse-3 wrote >> In the tips and tricks booklet, I added a simple chapter on hash. > > Cool! I committed a native english grammar review pass :) > > > > - > Cheers, > Sean > -- > Sent from:

Re: [Pharo-dev] Dark Mode List

2017-11-17 16:35 GMT+01:00 Stephane Ducasse : > ahhh. > :) > I think that we should have nice white theme and a nice dark new theme > for Pharo 70. > Because we need to see the difference. Since Pharo 60 was dark by default > Pharo 70 should be white by default so that

Re: [Pharo-dev] Pharo and special unary selectors

Parsing difficulty also means that it is harder for humans to understand, to explain to (new) users. It would be pretty strange to have binary selectors that are unary, is my first reaction. > On 17 Nov 2017, at 18:32, Thierry Goubier wrote: > > Le 17/11/2017 à

[Pharo-dev] [Pharo 7.0-dev] Build #304: 20704-remove-garbageCollect-from-PharoClassInstallermigrateClassestousing

There is a new Pharo build available! The status of the build #304 was: SUCCESS. The Pull Request #489 was integrated: "20704-remove-garbageCollect-from-PharoClassInstallermigrateClassestousing" Pull request url: https://github.com/pharo-project/pharo/pull/489 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #305: 20709-do-not-create-pharo-core-symlink-during-the-image-building

There is a new Pharo build available! The status of the build #305 was: SUCCESS. The Pull Request #492 was integrated: "20709-do-not-create-pharo-core-symlink-during-the-image-building" Pull request url: https://github.com/pharo-project/pharo/pull/492 Issue Url:

Re: [Pharo-dev] Little Chapter on Hash methods

Stephane Ducasse-3 wrote > In the tips and tricks booklet, I added a simple chapter on hash. Cool! I committed a native english grammar review pass :) - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Pharo and special unary selectors

2017-11-17 17:40 GMT+01:00 Gabriel Cotelli : > I would really like to see % removed as a binary selector and available to > use in unary or keyword ones. The only implementor in a Pharo 6 image is: > > % aNumber > > ^ self \\ aNumber > > +1, such alias has nothing to do

Re: [Pharo-dev] [ci-announces] CI capacity problems, help wanted !

Hi Bruno We will have a look. Now the failures/erasure of the configurations this summer did not really help us. We still not fully recovered. Once Pharo will be managed on git. I think that many of our community jobs will be migrated to travis and other services. Stef On Thu, Nov 16, 2017 at

Re: [Pharo-dev] Pharo Quality: raising the quality level in Pharo 7 and onwards

On Fri, Nov 17, 2017 at 2:48 PM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > It seems to me that you could technically enforce with github/travis: > - save the result of previous code critics > - pass the code critics on travis > - diff with previous > - reject any contribution

[Pharo-dev] [Pharo 7.0-dev] Build #307: 20715 Unused temps in RBRefactoringChangeTests, RPackageClassesSynchronisationTest, RPackageIncrementalTest, ...

There is a new Pharo build available! The status of the build #307 was: SUCCESS. The Pull Request #495 was integrated: "20715 Unused temps in RBRefactoringChangeTests, RPackageClassesSynchronisationTest, RPackageIncrementalTest, ..." Pull request url:

[Pharo-dev] [Pharo 7.0-dev] Build #306: 20714-atatput--atatifAbsentPut-should-not-use-Dictionary

There is a new Pharo build available! The status of the build #306 was: SUCCESS. The Pull Request #496 was integrated: "20714-atatput--atatifAbsentPut-should-not-use-Dictionary" Pull request url: https://github.com/pharo-project/pharo/pull/496 Issue Url:

Re: [Pharo-dev] Pharo and special unary selectors

If a valid Smalltalk method identifier contains only... [a-zA-Z][a-zA-Z0-9]* http://www.osdata.com/programming/firstprograms/valididentifiers.html then one option could be that unary symbols must touch the previous identifier, i.e. no intervening whitespace, 100% 20$ 40€ 12‰ portion%

Re: [Pharo-dev] Pharo and special unary selectors

Le 17 nov. 2017 1:03 PM, "Nicolas Cellier" < nicolas.cellier.aka.n...@gmail.com> a écrit : 2017-11-17 18:32 GMT+01:00 Thierry Goubier : > Le 17/11/2017 à 10:14, Nicolas Cellier a écrit : > >> >> >> 2017-11-17 17:40 GMT+01:00 Gabriel Cotelli

Re: [Pharo-dev] Pharo and special unary selectors

--- Begin Message --- Personnally, I against adding those special symbols.  They add close to nothing (except complexity in the parser) to what we can actually do! Besides, what does 30$ + 17$ add up to?  Oh!  Did I tell you it was actually $30USD + $17CAN ? :) - Benoît

Re: [Pharo-dev] Pharo and special unary selectors

Le 17/11/2017 à 11:08, Sven Van Caekenberghe a écrit : Parsing difficulty also means that it is harder for humans to understand, to explain to (new) users. Agreed. This is a significant issue in some programming languages. It would be pretty strange to have binary selectors that are unary,