March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Smacc debugger

by Tudor Girba

Hi, It is actually the economic reasoning that prevailed here. John was willing to invest effort to both work with and benefit from the Moose/GT environment. The consequence was that he built the GT extensions for SmaCC while Andrei and I offered a bit of support. In this process, we also got updates and fixes to several grammars that are now shipped with Moose. Furthermore, as John is the primary author of SmaCC it only makes sense that he gets to control what he maintains. As for the repository, I asked him kindly to keep it in SmalltalkHub at the beginning to make the integration with Moose cheaper and easier. Now, that the GitHub solution grows we can certainly consider moving it together with the rest of Moose. As for the need to have a fork of SmaCC, I think there is little need for that and John was always responsive to requests. Cheers, Doru > On Mar 29, 2017, at 6:21 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > So I browsed the mailing-list and I foind the mail of thierry saying that there is no difference. > I will try to tools in moose then. > > > On Wed, Mar 29, 2017 at 6:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ok I should say that I do not understand the differences and why there are two versions of Smacc. > So I will stop maintaining the tutorial because now may be I should revert what I wrote. > I was too stupid to do it in fact I should focus on my stuff and nothing else. > This saddens me a lot. > We are a small community and we split ourselves into little chunks. > I do not get why there is no notion of economy and sharing in our culture. > > Stef > > > > On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > OK > > I loaded Smacc from github as mentioned by thierry. > > > > Metacello new > > baseline: 'SmaCC'; > > repository: 'github://ThierryGoubier/SmaCC'; > > load > > > > Are there two configurationOfSmacc? > > May be we should only have one no? > > > > I have the impression that even thierry and jason working heavily with Smacc do not know that. > > And we should not force them to use Moose. At least we do not have to win > > anything with it. > > I did not mean to force anyone to use Moose. I just said it is already loaded there, in case you use it. > > Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry has another repository that he created before John moved his work to Pharo. But, now that he does work with Pharo Moose relies on his version. > > Cheers, > Doru > > > > > Stef > > > > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > They come with the ConfigurationOfSmaCC which is already in the Moose image. > > > > Doru > > > > > > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > > > Hi > > > > > > where can I load the Smacc gt extension and debugger extensions? > > > > > > Stef > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Speaking louder won't make the point worthier." > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > > > -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

March 29, 2017

Re: [Pharo-users] Smacc debugger

by Thierry Goubier

Hi Jimmie, Le 29/03/2017 Ã 20:07, Jimmie Houchin a Ã©crit : > What I don't understand from this thread, and my apologies if it was > expressed. But to me the question is not what or why happened in the > past. Rather what is the way to proceed ahead with a single canonical > source. This is what will benefit the community. What and where is that > source. I don't know. I will probably update the github repo by backporting the changes I'm interested in from the smalltalkhub repo, when I'll get the time to do it. There is little pressure to do so: both versions work perfectly well for its usual users, and they are close enough that documentation is the same for both. Tracking changes on the smalltalkhub repo is inconvenient, to say the least: this thing never sends anything to any watcher, to the difference of github, so you can't track anything about updates appearing there. On github, you can subscribe to updates... makes a world of a difference if you have to track a project. If you are still using an old parser on the previous SmaCC version (1.x), you'll have to get yet another SmaCC repository. Regards, Thierry > Shalom. > > > Jimmie Houchin > > > > On 03/29/2017 12:25 PM, Thierry Goubier wrote: >> >> >> 2017-03-29 18:07 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com >> <mailto:stepharo.self@gmail.com>>: >> >> Ok I should say that I do not understand the differences and why >> there are two versions of Smacc. >> So I will stop maintaining the tutorial because now may be I >> should revert what I wrote. >> I was too stupid to do it in fact I should focus on my stuff and >> nothing else. >> This saddens me a lot. >> We are a small community and we split ourselves into little chunks. >> I do not get why there is no notion of economy and sharing in our >> culture. >> >> >> I also don't know why it was done that way. And I don't want to spend >> energy fighting it. >> >> Thierry >> >> >> >> Stef >> >> >> >> On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse >> <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: >> > >> > OK >> > I loaded Smacc from github as mentioned by thierry. >> > >> > Metacello new >> > baseline: 'SmaCC'; >> > repository: 'github://ThierryGoubier/SmaCC'; >> > load >> > >> > Are there two configurationOfSmacc? >> > May be we should only have one no? >> > >> > I have the impression that even thierry and jason working >> heavily with Smacc do not know that. >> > And we should not force them to use Moose. At least we do >> not have to win >> > anything with it. >> >> I did not mean to force anyone to use Moose. I just said it is >> already loaded there, in case you use it. >> >> Moose relies on the ConfigurationOfSmaCC maintained by John. >> Thierry has another repository that he created before John >> moved his work to Pharo. But, now that he does work with Pharo >> Moose relies on his version. >> >> Cheers, >> Doru >> >> > >> > Stef >> > >> > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba >> <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> > They come with the ConfigurationOfSmaCC which is already in >> the Moose image. >> > >> > Doru >> > >> > >> > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: >> > > >> > > Hi >> > > >> > > where can I load the Smacc gt extension and debugger >> extensions? >> > > >> > > Stef >> > >> > -- >> > www.tudorgirba.com <http://www.tudorgirba.com> >> > www.feenk.com <http://www.feenk.com> >> > >> > "Speaking louder won't make the point worthier." >> > >> > >> > >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> www.feenk.com <http://www.feenk.com> >> >> "There are no old things, there are only old ways of looking >> at them." >> >> >> >> >> >> >> >

March 29, 2017

Re: Neural Networks in Pharo

by Alidra Abdelghani

Hi Oleksandr, Since you are interested in the implementation aspect of neural networks, may be you should take a look on heuristiclab (http://dev.heuristiclab.com/trac.fcgi/wiki) a general framework for developing heuristic algorithms (not only neural networks, actually). The interesting part is that the focus is on the implementation aspects too. The approach adopted by the developers is a Software Product Line one which seems to bring significant improvement to the way the code can be reused and adapted to different/new problems. Have a nice journey with Pharo ;) Abdelghani > On 21 Mar 2017, at 10:22, pharo-users-request(a)lists.pharo.org wrote: > > From: Oleksandr Zaytsev <olk.zaytsev(a)gmail.com <mailto:olk.zaytsev@gmail.com>> > To: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: [Pharo-users] Neural Networks in Pharo > Message-ID: > <CAEp0UzuU-sMvgJyWtQSuMOQFu1JX1joyy48U8s08XAfZix8JjA(a)mail.gmail.com <mailto:CAEp0UzuU-sMvgJyWtQSuMOQFu1JX1joyy48U8s08XAfZix8JjA@mail.gmail.com>> > Content-Type: text/plain; charset="utf-8" > > Hello. > > I'm implementing Neural Networks in Pharo as part of my thesis > (object-oriented approaches to neural networks implementation). It would be > really nice to receive some feedback. So if you have any ideas, > recommendations, or critique, please, write me. What are the existing > projects or common pitfalls that I should consider? Maybe, you can > recommend me some nice book or paper on a related topic. I would be > grateful for any kind of feedback. > > Here is the repository: http://smalltalkhub.com/#!/~Oleks/NeuralNetwork <http://smalltalkhub.com/#!/~Oleks/NeuralNetwork>. > It's not much, but I'm working on it. > > Yours sincerely, > Oleksandr

March 29, 2017

Re: [Pharo-users] Smacc debugger

by Jimmie Houchin

What I don't understand from this thread, and my apologies if it was expressed. But to me the question is not what or why happened in the past. Rather what is the way to proceed ahead with a single canonical source. This is what will benefit the community. What and where is that source. Shalom. Jimmie Houchin On 03/29/2017 12:25 PM, Thierry Goubier wrote: > > > 2017-03-29 18:07 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com > <mailto:stepharo.self@gmail.com>>: > > Ok I should say that I do not understand the differences and why > there are two versions of Smacc. > So I will stop maintaining the tutorial because now may be I > should revert what I wrote. > I was too stupid to do it in fact I should focus on my stuff and > nothing else. > This saddens me a lot. > We are a small community and we split ourselves into little chunks. > I do not get why there is no notion of economy and sharing in our > culture. > > > I also don't know why it was done that way. And I don't want to spend > energy fighting it. > > Thierry > > > Stef > > > > On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > Hi, > > > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse > <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > > > OK > > I loaded Smacc from github as mentioned by thierry. > > > > Metacello new > > baseline: 'SmaCC'; > > repository: 'github://ThierryGoubier/SmaCC'; > > load > > > > Are there two configurationOfSmacc? > > May be we should only have one no? > > > > I have the impression that even thierry and jason working > heavily with Smacc do not know that. > > And we should not force them to use Moose. At least we do > not have to win > > anything with it. > > I did not mean to force anyone to use Moose. I just said it is > already loaded there, in case you use it. > > Moose relies on the ConfigurationOfSmaCC maintained by John. > Thierry has another repository that he created before John > moved his work to Pharo. But, now that he does work with Pharo > Moose relies on his version. > > Cheers, > Doru > > > > > Stef > > > > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba > <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > > They come with the ConfigurationOfSmaCC which is already in > the Moose image. > > > > Doru > > > > > > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse > <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > > > > > Hi > > > > > > where can I load the Smacc gt extension and debugger > extensions? > > > > > > Stef > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > www.feenk.com <http://www.feenk.com> > > > > "Speaking louder won't make the point worthier." > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > www.feenk.com <http://www.feenk.com> > > "There are no old things, there are only old ways of looking > at them." > > > > > > >

March 29, 2017

Re: [Pharo-users] Smacc debugger

by Thierry Goubier

2017-03-29 18:07 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Ok I should say that I do not understand the differences and why there are > two versions of Smacc. > So I will stop maintaining the tutorial because now may be I should revert > what I wrote. > I was too stupid to do it in fact I should focus on my stuff and nothing > else. > This saddens me a lot. > We are a small community and we split ourselves into little chunks. > I do not get why there is no notion of economy and sharing in our culture. > I also don't know why it was done that way. And I don't want to spend energy fighting it. Thierry > > Stef > > > > On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> > >> > OK >> > I loaded Smacc from github as mentioned by thierry. >> > >> > Metacello new >> > baseline: 'SmaCC'; >> > repository: 'github://ThierryGoubier/SmaCC'; >> > load >> > >> > Are there two configurationOfSmacc? >> > May be we should only have one no? >> > >> > I have the impression that even thierry and jason working heavily with >> Smacc do not know that. >> > And we should not force them to use Moose. At least we do not have to >> win >> > anything with it. >> >> I did not mean to force anyone to use Moose. I just said it is already >> loaded there, in case you use it. >> >> Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry has >> another repository that he created before John moved his work to Pharo. >> But, now that he does work with Pharo Moose relies on his version. >> >> Cheers, >> Doru >> >> > >> > Stef >> > >> > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> > They come with the ConfigurationOfSmaCC which is already in the Moose >> image. >> > >> > Doru >> > >> > >> > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> > > >> > > Hi >> > > >> > > where can I load the Smacc gt extension and debugger extensions? >> > > >> > > Stef >> > >> > -- >> > www.tudorgirba.com >> > www.feenk.com >> > >> > "Speaking louder won't make the point worthier." >> > >> > >> > >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "There are no old things, there are only old ways of looking at them." >> >> >> >> >> >> >

March 29, 2017

Re: [Pharo-users] Smacc debugger

by Thierry Goubier

2017-03-29 18:21 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > So I browsed the mailing-list and I foind the mail of thierry saying that > there is no difference. > I will try to tools in moose then. > Probably: the +, *, ?, ( ) in the grammar don't work anymore. As I told you: very few differences. > On Wed, Mar 29, 2017 at 6:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Ok I should say that I do not understand the differences and why there >> are two versions of Smacc. >> So I will stop maintaining the tutorial because now may be I should >> revert what I wrote. >> I was too stupid to do it in fact I should focus on my stuff and nothing >> else. >> This saddens me a lot. >> We are a small community and we split ourselves into little chunks. >> I do not get why there is no notion of economy and sharing in our culture. >> > Thierry > >> Stef >> >> >> >> On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Hi, >>> >>> > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> > >>> > OK >>> > I loaded Smacc from github as mentioned by thierry. >>> > >>> > Metacello new >>> > baseline: 'SmaCC'; >>> > repository: 'github://ThierryGoubier/SmaCC'; >>> > load >>> > >>> > Are there two configurationOfSmacc? >>> > May be we should only have one no? >>> > >>> > I have the impression that even thierry and jason working heavily with >>> Smacc do not know that. >>> > And we should not force them to use Moose. At least we do not have to >>> win >>> > anything with it. >>> >>> I did not mean to force anyone to use Moose. I just said it is already >>> loaded there, in case you use it. >>> >>> Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry has >>> another repository that he created before John moved his work to Pharo. >>> But, now that he does work with Pharo Moose relies on his version. >>> >>> Cheers, >>> Doru >>> >>> > >>> > Stef >>> > >>> > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> >>> wrote: >>> > They come with the ConfigurationOfSmaCC which is already in the Moose >>> image. >>> > >>> > Doru >>> > >>> > >>> > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> > > >>> > > Hi >>> > > >>> > > where can I load the Smacc gt extension and debugger extensions? >>> > > >>> > > Stef >>> > >>> > -- >>> > www.tudorgirba.com >>> > www.feenk.com >>> > >>> > "Speaking louder won't make the point worthier." >>> > >>> > >>> > >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "There are no old things, there are only old ways of looking at them." >>> >>> >>> >>> >>> >>> >> >

March 29, 2017

Re: [Pharo-users] Smacc debugger

by Stephane Ducasse

So I browsed the mailing-list and I foind the mail of thierry saying that there is no difference. I will try to tools in moose then. On Wed, Mar 29, 2017 at 6:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ok I should say that I do not understand the differences and why there are > two versions of Smacc. > So I will stop maintaining the tutorial because now may be I should revert > what I wrote. > I was too stupid to do it in fact I should focus on my stuff and nothing > else. > This saddens me a lot. > We are a small community and we split ourselves into little chunks. > I do not get why there is no notion of economy and sharing in our culture. > > Stef > > > > On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> > >> > OK >> > I loaded Smacc from github as mentioned by thierry. >> > >> > Metacello new >> > baseline: 'SmaCC'; >> > repository: 'github://ThierryGoubier/SmaCC'; >> > load >> > >> > Are there two configurationOfSmacc? >> > May be we should only have one no? >> > >> > I have the impression that even thierry and jason working heavily with >> Smacc do not know that. >> > And we should not force them to use Moose. At least we do not have to >> win >> > anything with it. >> >> I did not mean to force anyone to use Moose. I just said it is already >> loaded there, in case you use it. >> >> Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry has >> another repository that he created before John moved his work to Pharo. >> But, now that he does work with Pharo Moose relies on his version. >> >> Cheers, >> Doru >> >> > >> > Stef >> > >> > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> > They come with the ConfigurationOfSmaCC which is already in the Moose >> image. >> > >> > Doru >> > >> > >> > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> > > >> > > Hi >> > > >> > > where can I load the Smacc gt extension and debugger extensions? >> > > >> > > Stef >> > >> > -- >> > www.tudorgirba.com >> > www.feenk.com >> > >> > "Speaking louder won't make the point worthier." >> > >> > >> > >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "There are no old things, there are only old ways of looking at them." >> >> >> >> >> >> >

March 29, 2017

Re: [Pharo-users] Smacc debugger

by Stephane Ducasse

Ok I should say that I do not understand the differences and why there are two versions of Smacc. So I will stop maintaining the tutorial because now may be I should revert what I wrote. I was too stupid to do it in fact I should focus on my stuff and nothing else. This saddens me a lot. We are a small community and we split ourselves into little chunks. I do not get why there is no notion of economy and sharing in our culture. Stef On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > OK > > I loaded Smacc from github as mentioned by thierry. > > > > Metacello new > > baseline: 'SmaCC'; > > repository: 'github://ThierryGoubier/SmaCC'; > > load > > > > Are there two configurationOfSmacc? > > May be we should only have one no? > > > > I have the impression that even thierry and jason working heavily with > Smacc do not know that. > > And we should not force them to use Moose. At least we do not have to win > > anything with it. > > I did not mean to force anyone to use Moose. I just said it is already > loaded there, in case you use it. > > Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry has > another repository that he created before John moved his work to Pharo. > But, now that he does work with Pharo Moose relies on his version. > > Cheers, > Doru > > > > > Stef > > > > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > > They come with the ConfigurationOfSmaCC which is already in the Moose > image. > > > > Doru > > > > > > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > > > Hi > > > > > > where can I load the Smacc gt extension and debugger extensions? > > > > > > Stef > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Speaking louder won't make the point worthier." > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > >

March 29, 2017

Re: [Pharo-users] Build instructions for building threaded 6.0 VM on linux

by Alistair Grant

Hi Estaban, On 29 March 2017 at 15:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > thatâs because you need to generate commit info. > this is usually a hook, but is not working super fine. > I have thi script in my root: > > genVersion.sh: > #! /bin/bash > > echo "`cat opensmalltalk-vm/platforms/Cross/vm/sqSCCSVersion.h | opensmalltalk-vm/.git_filters/RevDateURL.smudge`" > opensmalltalk-vm/platforms/Cross/vm/sqSCCSVersion.h > echo "`cat opensmalltalk-vm/platforms/Cross/plugins/sqPluginsSCCSVersion.h | opensmalltalk-vm/.git_filters/RevDateURL.smudge`" > opensmalltalk-vm/platforms/Cross/plugins/sqPluginsSCCSVersion.h > > > :P > > Esteban And up and running! Next step is to try and get the snap package to the point where I'm happy to post it on bintray for people to try. Thanks for your assistance! Alistair

March 29, 2017

Re: [Pharo-users] Build instructions for building threaded 6.0 VM on linux

by Ben Coman

On Wed, Mar 29, 2017 at 9:04 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > thatâs because you need to generate commit info. ahhhh. penny drops! I guess you mean "Important notice for developers" per... https://github.com/OpenSmalltalk/opensmalltalk-vm I was on a new machine and that was long forgotten. cheers -ben > this is usually a hook, but is not working super fine. > I have thi script in my root: > > genVersion.sh: > #! /bin/bash > > echo "`cat opensmalltalk-vm/platforms/Cross/vm/sqSCCSVersion.h | opensmalltalk-vm/.git_filters/RevDateURL.smudge`" > opensmalltalk-vm/platforms/Cross/vm/sqSCCSVersion.h > echo "`cat opensmalltalk-vm/platforms/Cross/plugins/sqPluginsSCCSVersion.h | opensmalltalk-vm/.git_filters/RevDateURL.smudge`" > opensmalltalk-vm/platforms/Cross/plugins/sqPluginsSCCSVersion.h > > > :P > > Esteban > > >> On 29 Mar 2017, at 15:02, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Ben, >> >> On 27 March 2017 at 01:37, Ben Coman <btc(a)openinworld.com> wrote: >>> On Mon, Mar 27, 2017 at 5:25 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> Trying to use the VM produces: >>>> >>>> THERE_BE_DRAGONS_HERE >>>> Your VM is too old for this image. Please download the latest VM. >>>> 26 March 2017 10:54:36.099174 pm >>> >>> Last night I built the 64-bit pharo-vm on OSX >>> and then trying to run 60451-64.image gave me the same error. >>> I didn't have time to look into it. >> >> Did you get a chance to resolve this? >> >> If not, can you (or someone) point me to where the VM prints its >> version information, i.e.: >> >> pharo --version >> >> I think I'll be able to trace back from there what the problem is. >> >> Thanks very much, >> Alistair >> > >

March 29, 2017