[Pharo-dev] [Pharo 7.0-dev] Build #614: 21415 Move primitive failure methods from Object to ProtoObject

There is a new Pharo build available! The status of the build #614 was: SUCCESS. The Pull Request #964 was integrated: "21415 Move primitive failure methods from Object to ProtoObject" Pull request url: https://github.com/pharo-project/pharo/pull/964 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #593: 21390-Do-not-store-any-non-literals-in-the-literal-array

> Am 25.02.2018 um 22:02 schrieb Stephane Ducasse : > > I really like this idea of read only literals :) > Tx for pushing it. +1 > >> On Thu, Feb 22, 2018 at 11:52 AM, Marcus Denker >> wrote: >> This fixes the Reflectivity compiler to not

[Pharo-dev] [Pharo 7.0-dev] Build #613: 21413 Cleanup JobTest

There is a new Pharo build available! The status of the build #613 was: SUCCESS. The Pull Request #962 was integrated: "21413 Cleanup JobTest" Pull request url: https://github.com/pharo-project/pharo/pull/962 Issue Url: https://pharo.fogbugz.com/f/cases/21413 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #612: 21420-The-XML-Test-reports-should-have-independent-filenames-for-each-CI-Node

There is a new Pharo build available! The status of the build #612 was: SUCCESS. The Pull Request #967 was integrated: "21420-The-XML-Test-reports-should-have-independent-filenames-for-each-CI-Node" Pull request url: https://github.com/pharo-project/pharo/pull/967 Issue Url:

Re: [Pharo-dev] Monticello file out bug during bootstrap

Hi Everyone, The following demonstrates the problem (and will allow me to provide an automated test when I submit a patch): | stream definition writer diskStore nonExistent | definition := MCMethodDefinition className: #DiskStore classIsMeta: true selector: #activeClass

[Pharo-dev] [Pharo 7.0-dev] Build #611: 21406 NumberParserTest should use "utilities" method protocol instead of utility

There is a new Pharo build available! The status of the build #611 was: SUCCESS. The Pull Request #956 was integrated: "21406 NumberParserTest should use "utilities" method protocol instead of utility" Pull request url: https://github.com/pharo-project/pharo/pull/956 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #610: 21409 NECTestClass should use utilities categories

There is a new Pharo build available! The status of the build #610 was: SUCCESS. The Pull Request #958 was integrated: "21409 NECTestClass should use utilities categories" Pull request url: https://github.com/pharo-project/pharo/pull/958 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #609: 21416 Cleanup AssocationTest

There is a new Pharo build available! The status of the build #609 was: SUCCESS. The Pull Request #965 was integrated: "21416 Cleanup AssocationTest" Pull request url: https://github.com/pharo-project/pharo/pull/965 Issue Url: https://pharo.fogbugz.com/f/cases/21416 Build Url:

Re: [Pharo-dev] Esteban's ChangeLog week of 19 February 2018

btw… reason why inform is being so small is because I’m investing a lot of time on a new UI for iceberg. and that’s a “meta-task”. I will try to split tasks on smaller ones :) Esteban > On 26 Feb 2018, at 11:47, Sean P. DeNigris wrote: > > EstebanLM wrote >> >>Now

[Pharo-dev] [Pharo 7.0-dev] Build #608: 21402-Removing-Transcript-Core-from-the-Bootstraped-Image

There is a new Pharo build available! The status of the build #608 was: SUCCESS. The Pull Request #951 was integrated: "21402-Removing-Transcript-Core-from-the-Bootstraped-Image" Pull request url: https://github.com/pharo-project/pharo/pull/951 Issue Url:

Re: [Pharo-dev] Esteban's ChangeLog week of 19 February 2018

EstebanLM wrote > > Now it should be there ;) Yes, it works. Thanks!! - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Monticello file out bug during bootstrap

Hi Guille and Stef, Stef, thanks also for your reply. All the information I was going to put there I've included below, so please treat is a combined reply. On 26 February 2018 at 09:51, Guillermo Polito wrote: > Hi Alistair, > > Can you provide some more context on

[Pharo-dev] [Pharo 7.0-dev] Build #607: 21410 Structure DebuggerActions package with Tags

There is a new Pharo build available! The status of the build #607 was: SUCCESS. The Pull Request #959 was integrated: "21410 Structure DebuggerActions package with Tags" Pull request url: https://github.com/pharo-project/pharo/pull/959 Issue Url:

Re: [Pharo-dev] [Vm-dev] OSSubprocess 0.2.5 fails in Pharo 6.1 64 bits (macOS)

Hmm, wait, I think these are two different issues :) I managed to successfully use OSSubprocess in 64bits with some tweaks. The problem is that OSSubprocess does some manual type coertions like assumming 32 bits: collectArgumentPointersInto: aPointer [...] aPointer nbUInt32AtOffset:

Re: [Pharo-dev] [Vm-dev] OSSubprocess 0.2.5 fails in Pharo 6.1 64 bits (macOS)

I'll try making a PR now to fix that. On Mon, Feb 26, 2018 at 10:19 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hmm, wait, I think these are two different issues :) > > I managed to successfully use OSSubprocess in 64bits with some tweaks. The > problem is that OSSubprocess does

Re: [Pharo-dev] "curl https://get.pharo.org/64 | bash" does not work (on Mac)

These pages are wrong (at least): http://pharo.org/download https://pharo.org/gnu-linux-installation-64 https://pharo.org/gnu-linux-installation On Sun, Feb 25, 2018 at 9:36 PM, Stephane Ducasse wrote: > which page? > >

Re: [Pharo-dev] Pull Request 20898-MultiByteFileStream-upToAll-does-not-work-correctly-with-UTF-8

Well, It looks like when you read tonel files with your changes there are some "invisible" characters left over in the stream. I think that first you should be able to reproduce the issue locally without bootstrapping by trying to import a tonel file in an image with your changes. Just take any

Re: [Pharo-dev] Monticello file out bug during bootstrap

Hi Alistair, Can you provide some more context on what are you trying to do and how? Generally you should not change anything in the bootstrap, just modify the classes you want to modify and commit them into the repository. The bootstrap will take care of it. The only cases when you need to