July 2014 - Pharo-dev - lists.pharo.org

pharo-contribution down?

by Yuriy Tymchuk

subj

July 18, 2014

503 on pharo-contribution CI

by Max Leske

Iâm getting a 503 when trying to access pharo-contribution CI. It was working until half an hour ago. Could someone take a look please? Cheers, Max

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by phil＠highoctane.be

I load it from the moose team on sth. Works for me, browser included. Le 18 juil. 2014 09:24, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > In the case of Moose, #development and #bleedingEdge are the same. > > Doru > > > On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> I think what is loaded by CI is dependent on the workflow of the project. >> IMHO for most projects loading #bleedingEdge is the best thing to do. >> >> Norbert >> >> Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >> >> It loads #development as any CI job should do. >> >> Doru >> >> >> On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> >> wrote: >> >>> Stephan Eggermont wrote >>> > And there is a image build at >>> > https://ci.inria.fr/pharo-contribution/job/PetitParser/ >>> >>> Interesting. I wonder what the ci is loading, because if I try to load >>> the >>> default group in Pharo 3.0, I get an error (hence I load 'Core' and have >>> no >>> problems) >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

July 18, 2014

Re: [Pharo-dev] [Pharo4] First Class Global Variables

by Marcus Denker

On 18 Jul 2014, at 08:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> I have added a first GlobalVar hierarchyâ¦ it has already the code generation methods but Opal is not yet forwarding >>> code generation (and the compiler does not yet compile bindings with the subclass). >>> >> >> update 40 095 contains changes to deeper integrate first class variables (Slots and first class Globals) int the system. >> >> 1) Both the binding in "Smalltalk globals" as well as all Class Variables are now instances of GlobalVariable. >> (I want to have both GlobalVariable and ClassVariable, but that is for later) >> >> e.g. >> >> Object binding class >> (SmalltalkImage classVariableNamed: 'ShutDownList') class >> >> all the Slots and Globals understand >> >> #definingClass -> returns the class defining the variable or "nil" for true globals >> #usingMethods -> all methods reading or writing the variable >> >> >> e.g. try (Point slotNamed: #x) usingMethods >> >> Next: >> >> -> Hook Opal to forward code generation for globals to the meta object > Done (not yet integrated): > https://pharo.fogbugz.com/f/cases/13584/Forward-code-generation-for-Globals… > >> -> use ClassVariable for class variables > Done (not yet integrated): > https://pharo.fogbugz.com/f/cases/13586/Class-Variables-should-be-ClassVari… > This is now in Pharo4 update 097 Marcus

July 18, 2014

[pharo-project/pharo-core]

by GitHub

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

July 18, 2014

[pharo-project/pharo-core] a31a27: 40097

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a31a276f780b15bfbd294c214a9f317ebb7ad35a https://github.com/pharo-project/pharo-core/commit/a31a276f780b15bfbd294c21… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-18 (Fri, 18 Jul 2014) Changed paths: M OpalCompiler-Core.package/OCLiteralVariable.class/instance/emitting/emitStore_.st M OpalCompiler-Core.package/OCLiteralVariable.class/instance/emitting/emitValue_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script97.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40097.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Slot.package/ClassVariable.class/instance/as yet unclassified/link_.st A Slot.package/ClassVariable.class/instance/meta-object-protocol/link_.st R Slot.package/GlobalVariable.class/instance/as yet unclassified/link_.st M Slot.package/GlobalVariable.class/instance/code generation/emitValue_.st A Slot.package/GlobalVariable.class/instance/meta-object-protocol/link_.st M Slot.package/LiteralVariable.class/README.md R Slot.package/LiteralVariable.class/instance/converting/asGlobalVariable.st M Slot.package/SlotClassBuilder.class/instance/accessing/sharedVariablesFromString_.st R Slot.package/TestGlobalVariable.class/README.md R Slot.package/TestGlobalVariable.class/definition.st R Slot.package/extension/ByteString/instance/asGlobalVariable.st R Slot.package/extension/Symbol/instance/asGlobalVariable.st M Traits.package/TClass.class/instance/class variables/addClassVarNamed_.st M Traits.package/TClass.class/instance/class variables/classVariableDefinitionString.st Log Message: ----------- 40097 13584 Forward code generation for Globals and Class Vars to meta object https://pharo.fogbugz.com/f/cases/13584 13586 Class Variables should be ClassVariables, not Globals https://pharo.fogbugz.com/f/cases/13586 http://files.pharo.org/image/40/40097.zip

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Tudor Girba

In the case of Moose, #development and #bleedingEdge are the same. Doru On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I think what is loaded by CI is dependent on the workflow of the project. > IMHO for most projects loading #bleedingEdge is the best thing to do. > > Norbert > > Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > It loads #development as any CI job should do. > > Doru > > > On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> Stephan Eggermont wrote >> > And there is a image build at >> > https://ci.inria.fr/pharo-contribution/job/PetitParser/ >> >> Interesting. I wonder what the ci is loading, because if I try to load the >> default group in Pharo 3.0, I get an error (hence I load 'Core' and have >> no >> problems) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > -- www.tudorgirba.com "Every thing has its own flow"

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Norbert Hartl

I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do. Norbert > Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > It loads #development as any CI job should do. > > Doru > > >> On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Stephan Eggermont wrote >> > And there is a image build at >> > https://ci.inria.fr/pharo-contribution/job/PetitParser/ >> >> Interesting. I wonder what the ci is loading, because if I try to load the >> default group in Pharo 3.0, I get an error (hence I load 'Core' and have no >> problems) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

July 18, 2014

Re: [Pharo-dev] SmalltalkHub and public write access

by Marcus Denker

On 18 Jul 2014, at 01:29, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Nicolas Petton wrote >> It should be working fine now. > > Thanks! That's important for contributions :) > Yes! Thanks a lot! Marcus

July 18, 2014

Re: [Pharo-dev] [Pharo4] First Class Global Variables

by Marcus Denker

>> >> I have added a first GlobalVar hierarchyâ¦ it has already the code generation methods but Opal is not yet forwarding >> code generation (and the compiler does not yet compile bindings with the subclass). >> > > update 40 095 contains changes to deeper integrate first class variables (Slots and first class Globals) int the system. > > 1) Both the binding in "Smalltalk globals" as well as all Class Variables are now instances of GlobalVariable. > (I want to have both GlobalVariable and ClassVariable, but that is for later) > > e.g. > > Object binding class > (SmalltalkImage classVariableNamed: 'ShutDownList') class > > all the Slots and Globals understand > > #definingClass -> returns the class defining the variable or "nil" for true globals > #usingMethods -> all methods reading or writing the variable > > > e.g. try (Point slotNamed: #x) usingMethods > > Next: > > -> Hook Opal to forward code generation for globals to the meta object Done (not yet integrated): https://pharo.fogbugz.com/f/cases/13584/Forward-code-generation-for-Globals… > -> use ClassVariable for class variables Done (not yet integrated): https://pharo.fogbugz.com/f/cases/13586/Class-Variables-should-be-ClassVari… Marcus

July 18, 2014