November 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] eec705: 60295

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: eec7051ba6c585770dbf8da6a793da4ed2cb33d7 https://github.com/pharo-project/pharo-core/commit/eec7051ba6c585770dbf8da6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-11-17 (Thu, 17 Nov 2016) Changed paths: M AST-Core.package/RBMethodNode.class/instance/testing/defines_.st A AST-Core.package/RBPragmaNode.class/instance/testing/defines_.st A AST-Tests-Core.package/RBParserTest.class/instance/tests/testQueryingPrimitiveErrorVar.st M Kernel.package/Context.class/instance/controlling/send_to_with_super_.st M RPackage-Core.package/RPackage.class/instance/class tags/addClassTag_.st M RPackage-Core.package/RPackageTag.class/instance/accessing/removeFromPackage.st M RPackage-Core.package/RPackageTag.class/instance/accessing/renameTo_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60294.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60295.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60294.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60295.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/FTArrayIndexColumn.class/README.md A Spec-Core.package/FTArrayIndexColumn.class/class/accessing/undefinedColumnWidth.st A Spec-Core.package/FTArrayIndexColumn.class/class/instance creation/id_.st M Spec-Core.package/FTArrayIndexColumn.class/definition.st A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/id.st A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/id_.st A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/width.st A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/widthOrUndefined.st A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/width_.st A Spec-Core.package/FTArrayIndexColumn.class/instance/layout/acquireWidth_.st A System-Announcements.package/ClassTagAdded.class/README.md A System-Announcements.package/ClassTagAdded.class/definition.st A System-Announcements.package/ClassTagAnnouncement.class/README.md A System-Announcements.package/ClassTagAnnouncement.class/class/instance creation/in_tag_.st A System-Announcements.package/ClassTagAnnouncement.class/definition.st A System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/package.st A System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/package_.st A System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/packagesAffected.st A System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/tag.st A System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/tag_.st A System-Announcements.package/ClassTagRemoved.class/README.md A System-Announcements.package/ClassTagRemoved.class/definition.st A System-Announcements.package/ClassTagRenamed.class/README.md A System-Announcements.package/ClassTagRenamed.class/class/instance creation/in_tag_to_.st A System-Announcements.package/ClassTagRenamed.class/definition.st A System-Announcements.package/ClassTagRenamed.class/instance/accessing/newName.st A System-Announcements.package/ClassTagRenamed.class/instance/accessing/newName_.st A System-Announcements.package/SystemAnnouncer.class/instance/triggering/classTagAdded_inPackage_.st A System-Announcements.package/SystemAnnouncer.class/instance/triggering/classTagRemoved_fromPackage_.st A System-Announcements.package/SystemAnnouncer.class/instance/triggering/classTagRenamed_inPackage_to_.st Log Message: ----------- 60295 19335 Syntax highlighting do not work on methods with primitives that uses "ec" https://pharo.fogbugz.com/f/cases/19335 19340 Can not step over methods with meta links https://pharo.fogbugz.com/f/cases/19340 19343 Spec is now dependent on FastTable https://pharo.fogbugz.com/f/cases/19343 19351 ClassTagAnnouncement is needed to describe operations with class tags https://pharo.fogbugz.com/f/cases/19351 http://files.pharo.org/image/60/60295.zip

Nov. 17, 2016

Re: [Pharo-dev] [Moose-dev] Re: Segfault on Moose 6.1 jobs

by Esteban Lorenzano

> On 17 Nov 2016, at 10:18, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Thanks Eliot, > > However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest <http://get.pharo.org/60+vmLatest>. The zip file (here: http://files.pharo.org/get-files/60/ <http://files.pharo.org/get-files/60/>) was created on October 12, 2016. > > Did you mean that I do not get the latest one for Pharo60? yes and no. this is the latest VM with the old process, before the merge with opensmalltalk-vm. Iâm finishing the merge process (it was painful), but I still didnât integrate it into the pharo building process. For the moment, you can download ârealâ latest VMs from here: https://bintray.com/estebanlm/pharo-vm/build/201611142324#files <https://bintray.com/estebanlm/pharo-vm/build/201611142324#files> Esteban > > Vincent > > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch <mailto:moose-dev-bounces@list.inf.unibe.ch>] De la part de Eliot Miranda > EnvoyÃ© : mercredi 16 novembre 2016 18:41 > Ã : Pharo Development List > Cc : Moose-related development > Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs > > Hi Vincent, > > On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: > Hello, > > I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6). > Please find attached the latest failing stack trace. > > Here are the 2 jobs that fails: > https://ci.inria.fr/moose/job/moose-6.1/345/console <https://ci.inria.fr/moose/job/moose-6.1/345/console> > https://ci.inria.fr/moose/job/moose-6.1/347/console <https://ci.inria.fr/moose/job/moose-6.1/347/console> > > It seems that they are not failing for the same reason. > > Maybe because the job is not using the latest VM? : > > pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] > Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 > > Yes, this is very old. I suggest you update to something around VMMaker 1776 at the start of November. Right now there is a little instability from the LLP64 work for Win64, otherwise I would recommend the tip. > > With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 > Revision: https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply(a)github.com <mailto:noreply@github.com>> Jenkins build #594 > Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux > plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/] > > 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.!!!" > > > > -- > _,,,^..^,,,_ > best, Eliot > > !!!************************************************************************************* > "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.!!!"

Nov. 17, 2016

Re: [Pharo-dev] [Moose-dev] Re: Segfault on Moose 6.1 jobs

by Blondeau Vincent

Thanks Eliot, However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest. The zip file (here: http://files.pharo.org/get-files/60/) was created on October 12, 2016. Did you mean that I do not get the latest one for Pharo60? Vincent De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de Eliot Miranda EnvoyÃ© : mercredi 16 novembre 2016 18:41 Ã : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs Hi Vincent, On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hello, I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6). Please find attached the latest failing stack trace. Here are the 2 jobs that fails: https://ci.inria.fr/moose/job/moose-6.1/345/console https://ci.inria.fr/moose/job/moose-6.1/347/console It seems that they are not failing for the same reason. Maybe because the job is not using the latest VM? : pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Yes, this is very old. I suggest you update to something around VMMaker 1776 at the start of November. Right now there is a little instability from the LLP64 work for Win64, otherwise I would recommend the tip. With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply(a)github.com<mailto:noreply@github.com>> Jenkins build #594 Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/] 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.!!!" -- _,,,^..^,,,_ best, Eliot !!!************************************************************************************* "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.!!!"

Nov. 17, 2016

Re: [Pharo-dev] Reacting to multi-selection changes in ListModel

by HernÃ¡n Morales Durand

And two years later... Is there any example out there where #whenMultiSelectionChanged: is working? I am working with Pharo 5.0, but I could backport the fix . Cheers, HernÃ¡n 2014-07-17 10:11 GMT-03:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, > > maybe someone can help me out with this. Iâm working with ListModel that > supports multiple selection and has autoDeselect turned off. Now Iâve tried > to use #whenSelectionChanged: but it doesnât give any data, > #whenMultiSelectionChanged: is not triggered at all, > #whenSelectedItemChanged: works as for single selection list. > > Iâd be very thankful for any help. > > Uko >

Nov. 16, 2016

Re: [Pharo-dev] [squeak-dev] Pragma keyword / selector / methodSelector

by Tobias Pape

On 16.11.2016, at 17:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Tobias, Hi Denis, > > On Wed, Nov 16, 2016 at 7:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > You force me to search archives. I hope anybody else does this :). > > Here is good answer why pragma instead of annotation: http://forum.world.st/Pragma-support-in-Squeak-Pharo-Cuis-td3243836.html#a3… > > Thanks. Igor gets to the technical justification; method annotations/pragmas/those funny things in angle brackets *can* tell a compiler to do things and yes, Tobias, you're right, they *are* also metadata. > > The /real/ answer as to why we should use Pragma rather than MethodAnnotation is explained by Wittgenstein; we use words to mean what we want them to mean. Pragma is now a term that has been used for the Smalltalk scheme for nearly twenty years. We had a discussion several years ago, even before the thread Denis references, where we agreed that MethodAnnotation was a better name but the effort to make the change was too great for almost all of us (myself included) and so we fell back into using Pragma, and when we write the idea up this year and I presented it at ESUG I went back to using Pragma. It's shorter, and it means what we want it to mean, which is whatever is between those angle brackets, and whatever we make our compilers to on recognising them. > > While the name Pragma may not be a perfect name, it does refer exactly to what we have, and it is short, and it is current. > Granted. But the scheme I proposed would (a) give us a new, supposedly better fitting interface, while (b) retaining the established interface under the established name. Best regards -Tobias > > 2016-11-16 15:46 GMT+01:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > On 11/15/16, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-11-15 21:58 GMT+01:00 Tobias Pape <Das.Linux(a)gmx.de>: > > > >> Here's my 2ct: > >> > >> 1. Pragmas aren't actually pragmas. They do not instruct the compiler to > >> do things (_except_ for primitive: and apicall:, but these are now > >> outliers). > >> They rather add metadata to a (compiled) method. > >> 2. The 'thing' (ie, class) should probably be named > >> MethodAnnotation > >> 3. We can have the cake and eat it to: > >> > >> Rename Pragma -> MethodAnnotation. > >> Make Pragma a new subclass of MethodAnnotation. > >> Make MethodAnnotation implement > >> #methodSelector > >> #annotationSelector (or #selector, if it must be) > >> Make Pragma implement > >> #selector > >> #keywords > >> > > > > I remember long discussion about Pragma vs Annotation name where Igor won > > completely :)). Conclusion was that Pragma is a right name. > > Is there a summary of this discussion available? > > --Hannes > > > > > > > > > -- > _,,,^..^,,,_ > best, Eliot

Nov. 16, 2016

Re: [Pharo-dev] Segfault on Moose 6.1 jobs

by Eliot Miranda

Hi Vincent, On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Hello, > > > > I would like to report some random segfaults happing during the build of > the Moose 6.1 image (based on Pharo 6). > > Please find attached the latest failing stack trace. > > > > Here are the 2 jobs that fails: > > https://ci.inria.fr/moose/job/moose-6.1/345/console > > https://ci.inria.fr/moose/job/moose-6.1/347/console > > > > It seems that they are not failing for the same reason. > > > > Maybe because the job is not using the latest VM? : > > > > pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 > [Production Spur ITHB VM] > > Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 > uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 > Yes, this is very old. I suggest you update to something around VMMaker 1776 at the start of November. Right now there is a little instability from the LLP64 work for Win64, otherwise I would recommend the tip. > With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 > uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 > > Revision: https://github.com/pharo-project/pharo-vm.git Commit: > 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 > By: GitHub <noreply(a)github.com> Jenkins build #594 > > Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep > 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux > > plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: > /builds/workspace/moose-6.1/pharo-vm/] > > > > 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.!!!" > -- _,,,^..^,,,_ best, Eliot

Nov. 16, 2016

Re: [Pharo-dev] Windows 64 bits VM?

by Eliot Miranda

Hi Gabriel, my understanding is that Nicolas has the vm working in a fork. We are integrating the changes. Win64 is LLP64 (sizeof(long) == sizeof(int) == 4) which is problematic. I'm currently looking at a few regressions in the Squeak test suite before integrating, If you want to follow, subscribe to vm-dev; that's where the vm is discussed. Best, Eliot _,,,^..^,,,_ (phone) > On Nov 16, 2016, at 2:38 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Ok. Just let me know when it became available. I can help testing it. > > >> On Nov 16, 2016 05:08, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: >> >> > On 16 Nov 2016, at 00:01, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >> > >> > Hi, >> > Is there a Windows 64 bits VM ready to test? I couldn't find one, just the MacOs and Linux versions. >> >> there are no win64 versions for now (is been a huge effort to make them work). >> yesterday Nicolas Cellier announced he managed to build a stack 64bits that do not crashâ¦ 64bit cog is on his way, but it will take time. >> >> Esteban >> >> > >> > Regards, >> > Gabriel >> > >> >>

Nov. 16, 2016

Segfault on Moose 6.1 jobs

by Blondeau Vincent

Hello, I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6). Please find attached the latest failing stack trace. Here are the 2 jobs that fails: https://ci.inria.fr/moose/job/moose-6.1/345/console https://ci.inria.fr/moose/job/moose-6.1/347/console It seems that they are not failing for the same reason. Maybe because the job is not using the latest VM? : pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply(a)github.com> Jenkins build #594 Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/] 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.!!!"

Nov. 16, 2016

Re: [Pharo-dev] Windows 64 bits VM?

by Gabriel Cotelli

Ok. Just let me know when it became available. I can help testing it. On Nov 16, 2016 05:08, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: > > > On 16 Nov 2016, at 00:01, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > > > Hi, > > Is there a Windows 64 bits VM ready to test? I couldn't find one, just > the MacOs and Linux versions. > > there are no win64 versions for now (is been a huge effort to make them > work). > yesterday Nicolas Cellier announced he managed to build a stack 64bits > that do not crashâ¦ 64bit cog is on his way, but it will take time. > > Esteban > > > > > Regards, > > Gabriel > > > > >

Nov. 16, 2016

[pharo-project/pharo-core]

by GitHub

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

Nov. 16, 2016