- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Images, VMs and 32 vs 64bit
by Peter UhnÃ¡k April 10, 2018

April 10, 2018

> images for different platforms (Mac, Linux, Windows) yes It is the responsibility of the VM to contain the differences. Note that there's some "platform-specific" code, but the image contains the code for all platforms at once. Generally speaking you can code on one platform, copy the image files to another and continue your work (although doing this can cause trouble, as e.g. some file paths may now point to non-existing locations). You can download the images independently of the platform too (e.g. Pharo 6 images: http://files.pharo.org/image/60/ ) > VMs (32bit, 64bit) yes? the files are different, but I don't know if there's code difference, or if the images are just built with different memory layouts Peter On Wed, Apr 11, 2018 at 12:13 AM, Benoit St-Jean via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Bcc: > Date: Tue, 10 Apr 2018 22:13:18 +0000 (UTC) > Subject: Images, VMs and 32 vs 64bit > I was wondering if images for different platforms (Mac, Linux, Windows) > and VMs (32bit, 64bit) are, code-wise, the same? By "the same", I mean do > they all have the exact same code base or some classes/methods are in some > and not in others or different? > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

2 1

DateAndTime Offset Bug Proposal
by Sean P. DeNigris April 10, 2018

April 10, 2018

I was bitten by this very annoying bug again. As most of us probably know due to the steady stream of confused ML posts in the past, the bug in summary is that we have an incomplete timezone implementation that doesn't properly take into account historical DST changes. This flares up without warning especially when DST toggles. I created a wiki page to document the situation: https://github.com/seandenigris/pharo/wiki/Time-Zone-Fiasco Here's an example blowup: at 11:59pm before DST changes, eval aDate := '1/1/1901' asDate. Now, wait two minutes and at 12:01am eval self assert: '1/1/1901' asDate = aDate andâ¦ whammo, an exception! The "different" offsets render equal dates unequal depending on when the objects were created. The more I think about it, the more I think that we should just assume UTC for all Date[AndTime]s that don't explicitly specify an offset, rather than pretend to set an offset which is only sometimes correct. More advanced users can use one of the available libraries to get full timezone support. What do you think? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

11 27

[Pharo 7.0-dev] Build #759: 21680-haltIfTest-and-haltIfNotTest-and-comments
by ci-pharo-ci-jenkins2＠inria.fr April 10, 2018

April 10, 2018

There is a new Pharo build available! The status of the build #759 was: SUCCESS. The Pull Request #1187 was integrated: "21680-haltIfTest-and-haltIfNotTest-and-comments" Pull request url: https://github.com/pharo-project/pharo/pull/1187 Issue Url: https://pharo.fogbugz.com/f/cases/21680 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Metacello/Iceberg Error: IceUndefinedRemote DNU #projectPath
by Sean P. DeNigris April 9, 2018

April 9, 2018

I was loading a project via: Metacello new baseline: 'BabyPhexample'; repository: 'github://seandenigris/Baby-Phexample/repository'; onConflict: [ :ex | ex allow ]; load. into a Moose 6.1 image obtained from Launcher which already contained StateSpecs and got this: IceUndefinedRemote(Object)>>doesNotUnderstand: #projectPath IceMetacelloRepositoryAdapter>>projectPath IceMetacelloRepositoryAdapter>>hasNoLoadConflicts: MetacelloRepositorySpec>>hasNoLoadConflicts: MetacelloRepositoriesSpec>>hasNoLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloGenericProjectSpec)>>hasNoLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>hasNoLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloProjectSpec)>>hasLoadConflicts: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>hasConflictWithBaselineSpec: MetacelloMCBaselineOfProjectSpec>>hasConflictWithProjectSpec: MetacelloProjectRegistration>>hasLoadConflicts: Ideas? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 2

Multiple Inheritance
by Sean P. DeNigris April 9, 2018

April 9, 2018

I was just thinking about all the freedom brought by stateful traits, and the thought occurred: why not just simplify and remove another hurdle by having multiple inheritance with the conflict resolution and scoping of traits? Forgive me if I'm missing something obviousâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 7.0-dev] Build #758: 21682-DropListPresenter-ignores-disable-before-it-is-built
by ci-pharo-ci-jenkins2＠inria.fr April 9, 2018

April 9, 2018

There is a new Pharo build available! The status of the build #758 was: FAILURE. The Pull Request #1185 was integrated: "21682-DropListPresenter-ignores-disable-before-it-is-built" Pull request url: https://github.com/pharo-project/pharo/pull/1185 Issue Url: https://pharo.fogbugz.com/f/cases/21682 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] New Pharo 6.1 version
by Esteban Lorenzano April 9, 2018

April 9, 2018

https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1 <https://pharo.fogbugz.com/f/cases/20944/Integrate-Epicea-8-2-8-in-Ph6-1>

8 12

[Pharo 7.0-dev] Build #757: 21681-expandMacrosWith-shouldnt-truncate-strings
by ci-pharo-ci-jenkins2＠inria.fr April 9, 2018

April 9, 2018

There is a new Pharo build available! The status of the build #757 was: SUCCESS. The Pull Request #1184 was integrated: "21681-expandMacrosWith-shouldnt-truncate-strings" Pull request url: https://github.com/pharo-project/pharo/pull/1184 Issue Url: https://pharo.fogbugz.com/f/cases/21681 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 2 April 2018
by estebanlm＠gmail.com April 9, 2018

April 9, 2018

Hello! This is my weekly ChangeLog, from 2 April 2018 to 8 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=2/4/2018&to=8/4/2018 ChangeLog ========= 5 April 2018: ------------- * I closed [issue 593](https://github.com/pharo-vcs/iceberg/issues/593), revert a change is not refreshing changes list. * closed [issue 599](https://github.com/pharo-vcs/iceberg/issues/599), add fetch to remote entry in repository view. * fixed [case: 21676](https://pharo.fogbugz.com/f/cases/21676) (this is needed when using tabs). ... and made a backport for Pharo 6.1 [case: 21679](https://pharo.fogbugz.com/f/cases/21679) . * VM and CI : I made a pass to disable old projects still running in the Pharo Jenkins [http://ci.pharo.org](http://ci.pharo.org) . I don't know why they were still running, but that's wrong and they were consuming resources we need :) * I finished [issue 596](https://github.com/pharo-vcs/iceberg/issues/596) : Convert metacello plugin. * I created a github project to follow the work I'm doing with the new Iceberg UI (callled "Tip" :P). You can see it here: [https://github.com/pharo-vcs/iceberg/projects/2](https://github.com/pharo-v… I'm polishing (with the help of Guille and Pablo) the last details before "going public" in a test release. * I will resume posting actions here :) cheers! Esteban

1 0

April 8, 2018

Hello Armel The pharo board is not the list to ask questions and get some help. You can send the mail to Pharo Dev <pharo-dev(a)lists.pharo.org> or Pharo-users(a)lists.pharo.org You can also have direct discussion over discord http://discord.gg/Sj2rhxn <http://discord.gg/Sj2rhxn> Now if you want to have help describe clearly - Your OS - what you did? which version of Pharo, which version of the image Pharo 6.1? - did you use the PharoLauncher? Stef > On 8 Apr 2018, at 16:57, feav feav <feavfeav(a)gmail.com> wrote: > > Error. Could not determine platform's libc path for VM. > Try forcing $PLATFORMLIBDIR in /home/pi/pharo/pharo64/pharo/bin/pharo, based on LIBC_SO. > > Cordialement, Armel EMBOLO > <https://accounts.google.com/SignOutOptions?hl=fr&continue=https://mail.goog…> > IngÃ©nieur de travaux en Informatique de Gestion / Analyste programmeur > ElÃ¨ve IngÃ©nieur de Conception en GÃ©nie Logiciel > UniversitÃ© de Maroua, Ecole Nationale SupÃ©rieure Polytechnique de Maroua (ex ISS) > Facebook : Armel Embolo <https://www.facebook.com/armel.embolo> > Linkedin : armel embolo <https://www.linkedin.com/profile/view?id=AAMAABYswuMBn33mi4o_x8R49OxfxiIQVA…> > Tel : (+237) 650231339/698594740 -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 1