- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoV40.sources for 40606

by Tudor Girba

Is there anything we can do to help now? Doru On Mon, Apr 13, 2015 at 4:17 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 13 Apr 2015, at 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > We have to generate a new .source file. We will do that for 40606. > > This means that there will be two versions of 40606: one that has a V3 > Sources and one with a V4 source. > To not get confused, the best is to wait for 607. > > > Ok: > > -> sources file is on > http://files.pharo.org/sources/ > > -> the latest image (40606) use it: > > http://files.pharo.org/image/40/latest.zip > > Next: > > - fix get.pharo.org > - fix the scripts that build the downloads > - do a 607 > > > We did it all. > > Result: it is all broken. We will revert it all. > > What do we learn from it? The artefact on the build server needs to be the > artefact of release. > Everything that does not support this needs to be changes. > > Marcus > > -- www.tudorgirba.com "Every thing has its own flow"

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> On 13 Apr 2015, at 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> We have to generate a new .source file. We will do that for 40606. >> >> This means that there will be two versions of 40606: one that has a V3 Sources and one with a V4 source. >> To not get confused, the best is to wait for 607. >> > > Ok: > > -> sources file is on > http://files.pharo.org/sources/ <http://files.pharo.org/sources/> > > -> the latest image (40606) use it: > > http://files.pharo.org/image/40/latest.zip <http://files.pharo.org/image/40/latest.zip> > > Next: > > - fix get.pharo.org <http://get.pharo.org/> > - fix the scripts that build the downloads > - do a 607 We did it all. Result: it is all broken. We will revert it all. What do we learn from it? The artefact on the build server needs to be the artefact of release. Everything that does not support this needs to be changes. Marcus

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Marcus Denker

> We have to generate a new .source file. We will do that for 40606. > > This means that there will be two versions of 40606: one that has a V3 Sources and one with a V4 source. > To not get confused, the best is to wait for 607. > Ok: -> sources file is on http://files.pharo.org/sources/ <http://files.pharo.org/sources/> -> the latest image (40606) use it: http://files.pharo.org/image/40/latest.zip <http://files.pharo.org/image/40/latest.zip> Next: - fix get.pharo.org <http://get.pharo.org/> - fix the scripts that build the downloads - do a 607 Marcus

April 13, 2015

[pharo-project/pharo-core]

by GitHub

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

April 13, 2015

[pharo-project/pharo-core] 48f348: 40606

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 48f348978104f3ab3b989df184249d9162e2e812 https://github.com/pharo-project/pharo-core/commit/48f348978104f3ab3b989df1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-13 (Mon, 13 Apr 2015) Changed paths: M Kernel.package/Context.class/instance/accessing/tempNamed_.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamed_in_.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/debugging/methodScope.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/lookupTempVector_inContext_.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/variableNamed_ifAbsent_.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/addCopiedTempToAllScopesUpToDefVector_.st A OpalCompiler-Core.package/OCAbstractScope.class/instance/accessing/variableNamed_.st A OpalCompiler-Core.package/OCAbstractScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCClassScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCClassScope.class/instance/lookup/variableNamed_ifAbsent_.st R OpalCompiler-Core.package/OCCopyingTempVariable.class/instance/debugging/definingScope.st M OpalCompiler-Core.package/OCCopyingTempVariable.class/instance/debugging/indexInTempVectorFromIR_.st A OpalCompiler-Core.package/OCCopyingTempVariable.class/instance/temp vector/indexFromIR.st A OpalCompiler-Core.package/OCInstanceScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCInstanceScope.class/instance/lookup/variableNamed_ifAbsent_.st A OpalCompiler-Core.package/OCMethodScope.class/instance/testing/methodScope.st A OpalCompiler-Core.package/OCOptimizedBlockScope.class/instance/accessing/lookupVar_inContext_.st A OpalCompiler-Core.package/OCRequestorScope.class/instance/lookup/lookupVar_inContext_.st A OpalCompiler-Core.package/OCRequestorScope.class/instance/lookup/variableNamed_ifAbsent_.st M OpalCompiler-Core.package/OCTempVariable.class/instance/debugging/indexFromIR.st M OpalCompiler-Core.package/OCTempVariable.class/instance/debugging/readFromContext_scope_.st A OpalCompiler-Core.package/OCTempVariable.class/instance/debugging/searchFromContext_scope_.st M OpalCompiler-Core.package/OCTempVariable.class/instance/debugging/writeFromContext_scope_value_.st A OpalCompiler-Core.package/OCVectorTempVariable.class/instance/debugging/indexFromIR.st M OpalCompiler-Core.package/OCVectorTempVariable.class/instance/debugging/readFromContext_scope_.st A OpalCompiler-Core.package/OCVectorTempVariable.class/instance/debugging/searchFromContext_scope_.st A OpalCompiler-Tests.package/ManifestOpalCompilerTests.class/README.md A OpalCompiler-Tests.package/ManifestOpalCompilerTests.class/definition.st A OpalCompiler-Tests.package/ManifestOpalCompilerTests.class/instance/code-critics/ruleExtraBlockRuleV1FalsePositive.st A OpalCompiler-Tests.package/ManifestOpalCompilerTests.class/instance/code-critics/ruleGuardClauseRuleV1FalsePositive.st A OpalCompiler-Tests.package/ManifestOpalCompilerTests.class/instance/code-critics/ruleOnlyReadOrWrittenTemporaryRuleV1FalsePositive.st A OpalCompiler-Tests.package/ManifestOpalCompilerTests.class/instance/code-critics/ruleTempsReadBeforeWrittenRuleV1FalsePositive.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/README.md A OpalCompiler-Tests.package/OCContextTempMappingTest.class/definition.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingMultipleVariablesInVector.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingTempsVectorInBlock.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingTempsVectorInBlock2.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingTempsVectorInBlock3.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingVariablesInBlock.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingVariablesInOptimizedBlock.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/tests/testAccessingVariablesInOptimizedBlock2.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script605.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script606.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40605.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40606.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40606 14606 Cant see some variables values while debugging closure https://pharo.fogbugz.com/f/cases/14606 http://files.pharo.org/image/40/40606.zip

April 13, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Sean P. DeNigris

Sean P. DeNigris wrote > I did not even know we had these I even searched the ml archive for "Gentoo" and did not find a single reference to a package! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Shorter-Pharo-Launcher-download-link-tp4818944p481932… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 13, 2015

[pharo-project/pharo-core]

by GitHub

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

April 13, 2015

[pharo-project/pharo-core] d2a17d: 40605

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d2a17d28e41914dfbf7b8d1e15e3f16a7b78d46e https://github.com/pharo-project/pharo-core/commit/d2a17d28e41914dfbf7b8d1e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-13 (Mon, 13 Apr 2015) Changed paths: A MonticelloGUI.package/MCFileRepositoryInspector.class/instance/private/refresh.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script604.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script605.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40604.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40605.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40605 15335 method lost in last monticello change https://pharo.fogbugz.com/f/cases/15335 http://files.pharo.org/image/40/40605.zip

April 13, 2015

Re: [Pharo-dev] PharoV40.sources for 40606

by Tudor Girba

Great. Thanks for the heads up. Cheers, Doru On Mon, Apr 13, 2015 at 3:03 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > We have to generate a new .source file. We will do that for 40606. > > This means that there will be two versions of 40606: one that has a V3 > Sources and one with a V4 source. > To not get confused, the best is to wait for 607. > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"

April 13, 2015

Re: [Pharo-dev] Using an Associative array instead of a dictionnary ?

by Esteban Lorenzano

> On 13 Apr 2015, at 14:56, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi everyone ! > > I work on pillar and I saw that all the parameters are store inside an > associative array. > Do we have an advantage doing that ? Because it would be more > convinient to use a Dictionnary I think but maybe i'm missing > something. probably order. but now you can use OrderedDictionary to supply that. Esteban > > -- > Cheers > Cyril Ferlicot >

April 13, 2015