- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo Association has a new Website!

by Marcus Denker

> On 8 Dec 2016, at 15:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> >>> Accepting Bitcoin payments would be a plus ;-) (https://bitpay.com/tour <https://bitpay.com/tour>) >>> >> > > Hi, > > I have setup bitpay. This means we can now accept bitcoin, to pay by bitcoin, > for now please select âofflineâ payment and then send a mail to > association(a)pharo.org <mailto:association@pharo.org> > > and we will generate a bitcoin invoice. (we can integrate it a bit better later). > Hello, I now - added a link to donate by bitpay to https://association.pharo.org/Donate - added payments links to the invoice that the system generates for paying the membership. Marcus

Dec. 12, 2016

[pharo-project/pharo-core]

by GitHub

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

Dec. 12, 2016

[pharo-project/pharo-core] 2da393: 50765

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 2da393a0b6aa8f06137bbfb92b7d35b0c02a8c30 https://github.com/pharo-project/pharo-core/commit/2da393a0b6aa8f06137bbfb9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-12 (Mon, 12 Dec 2016) Changed paths: M Kernel.package/Delay.class/class/settings/delaySchedulerClass_.st A Kernel.package/ManifestKernel.class/class/code-critics/ruleRBBadMessageRuleV1FalsePositive.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50764.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50765.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50764.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50765.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50765 19435 Silently ignore loading DelayScheduler setting when its the same as existing (Pharo 5 backport) https://pharo.fogbugz.com/f/cases/19435 http://files.pharo.org/image/50/50765.zip

Dec. 12, 2016

Re: [Pharo-dev] Set internal array size

by Marcus Denker

> On 12 Dec 2016, at 14:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 12 Dec 2016, at 18:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 1 Dec 2016, at 11:41, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >>> >>> >>>> Le 1 dÃ©c. 2016 Ã 15:04, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : >>>> >>>> The idea that a set is always created with a minimal size is because we always add at least some elements >>> >>> not always. You know in some cases 80% of the time, your instances will have an empty Set and with some values for the remaining 20%. >>> If you check in Moose, you should find a lot this pattern. >> >> It would be interesting to play around with these thingsâ¦ the problem is that they are very context dependent, so there is lots >> of questions what to do (more a research topic than something one can solve nowâ¦). >> >> What we should do: >> >> -> the size should be 5, like it is for Dictionaries We need to unify the two version of the method that calculate the initial size. >> Issue tracker: https://pharo.fogbugz.com/f/cases/19458/unify-sizeFor-for-HashedCollection-… >> What we could do: >> >> -> provide a version of ânewâ that actually makes explicity a small array of size 1. For the case where the user knows that >> the Set will be empty most of the time. > > There could be an #empty class method for that. > And one could overwrite the #with: class method to create a singleton. https://pharo.fogbugz.com/f/cases/19459/add-empty-instance-creation-method <https://pharo.fogbugz.com/f/cases/19459/add-empty-instance-creation-method> (just the issues, no code) Marcus

Dec. 12, 2016

Re: [Pharo-dev] Set internal array size

by Sven Van Caekenberghe

> On 12 Dec 2016, at 18:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 1 Dec 2016, at 11:41, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >> >>> Le 1 dÃ©c. 2016 Ã 15:04, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : >>> >>> The idea that a set is always created with a minimal size is because we always add at least some elements >> >> not always. You know in some cases 80% of the time, your instances will have an empty Set and with some values for the remaining 20%. >> If you check in Moose, you should find a lot this pattern. > > It would be interesting to play around with these thingsâ¦ the problem is that they are very context dependent, so there is lots > of questions what to do (more a research topic than something one can solve nowâ¦). > > What we should do: > > -> the size should be 5, like it is for Dictionaries We need to unify the two version of the method that calculate the initial size. > > What we could do: > > -> provide a version of ânewâ that actually makes explicity a small array of size 1. For the case where the user knows that > the Set will be empty most of the time. There could be an #empty class method for that. And one could overwrite the #with: class method to create a singleton. > Marcus

Dec. 12, 2016

Re: [Pharo-dev] Set internal array size

by Marcus Denker

> On 1 Dec 2016, at 11:41, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > >> Le 1 dÃ©c. 2016 Ã 15:04, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : >> >> The idea that a set is always created with a minimal size is because we always add at least some elements > > not always. You know in some cases 80% of the time, your instances will have an empty Set and with some values for the remaining 20%. > If you check in Moose, you should find a lot this pattern. It would be interesting to play around with these thingsâ¦ the problem is that they are very context dependent, so there is lots of questions what to do (more a research topic than something one can solve nowâ¦). What we should do: -> the size should be 5, like it is for Dictionaries We need to unify the two version of the method that calculate the initial size. What we could do: -> provide a version of ânewâ that actually makes explicity a small array of size 1. For the case where the user knows that the Set will be empty most of the time. Marcus

Dec. 12, 2016

[pharo-project/pharo-core]

by GitHub

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

Dec. 12, 2016

[pharo-project/pharo-core] ed3ccb: 60324

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ed3ccb853824ab06940808cd93e649394b2bbec8 https://github.com/pharo-project/pharo-core/commit/ed3ccb853824ab06940808cd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-12 (Mon, 12 Dec 2016) Changed paths: M AST-Core.package/RBArrayNode.class/instance/matching/match_inContext_.st M AST-Core.package/RBPatternVariableNode.class/instance/accessing/parent_.st A AST-Tests-Core.package/RBParseTreeSearcherTest.class/instance/tests - to de refined/testDynamicArrayWithStatementListPattern.st A Reflectivity-Tests.package/ReflectivityExamples.class/instance/examples/exampleSendNoReturn.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifyReceiverOnSendWithArguments.st M Rubric.package/RubTextSegmentIconDisplayer.class/instance/event handling/invokeIconMenuOfSegments_event_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60323.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60324.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60323.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60324.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60324 19445 Pattern code ArrayNode matching failure https://pharo.fogbugz.com/f/cases/19445 18935 Rubric warning are not DarkTheme friendly https://pharo.fogbugz.com/f/cases/18935 19455 Testcase for reify receiver for before links https://pharo.fogbugz.com/f/cases/19455 http://files.pharo.org/image/60/60324.zip

Dec. 12, 2016

Crash.dmp not created on windows

by Blondeau Vincent

Hello, Since the release of the spur vm, the crash dump file (crash.dmp) is not generated when the image crashes under Windows (7 especially). Now, I have an image I cannot use because its crashed at startup and I cannot report a bug to VM developers in the purpose to resolve the crash. An issue on this has been opened almost for one year: https://pharo.fogbugz.com/f/cases/17506/when-an-Image-crashes-a-crash-dmp-f… Does the creation of this crash.dmp is planned? Thanks in advance, Cheers, Vincent !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Dec. 12, 2016

REMEMBER: Tomorrow 13/12 16h UTC TechTalk featuring Iceberg by Nico Passerini

by Esteban Lorenzano

Hi, Everything is in the subject :) Tomorrow we will handle a new TechTalk, this time to talk about Iceberg, the new SCM tool for Pharo. Since Nico will to also a âtourâ about what is implemented and how we expect the tool will be used, this time we will try to stream a public stream so people can watchâ¦ and participation, questions, etc. will be handled through discord, as usual. I will send links to both video and discord as soon as we have it :) cheers, Esteban

Dec. 12, 2016