- Pharo-users - lists.pharo.org

Re: [Pharo-users] Traits, method flatten

by Stephane Ducasse

can you show us the code? On Tue, Apr 11, 2017 at 7:08 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > When I load with Monticello classes with traits, all the traits methods > are duplicated in the class. > > I got this problem with 4.0 then now with 5.0 > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

April 11, 2017

Traits, method flatten

by Hilaire

Hi, When I load with Monticello classes with traits, all the traits methods are duplicated in the class. I got this problem with 4.0 then now with 5.0 Hilaire -- Dr. Geo http://drgeo.eu

April 11, 2017

Re: [Pharo-users] Pharo image freeze and "Alt-." has no effect

by Steven RÃ©mot

It looks like the freeze is not present on the latest dev release Ben. I will tell you if it just takes time to appear but it looks much more stable. Thanks! Steven RÃ©mot Le sam. 8 avr. 2017 Ã 02:46, Ben Coman <btc(a)openinworld.com> a Ã©crit : > Just for starters, can you try with dev-latest VM & Image... > * > http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20170… > * http://files.pharo.org/image/60/60463.zip > > cheers -ben > > On Fri, Apr 7, 2017 at 7:05 PM, Steven RÃ©mot <steven.remot(a)gmail.com> > wrote: > > I'm on Linux (Ubuntu 15.10), and the output of pharo -v is: > > 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] > CoInterpreter VMMaker.oscog-eem.1855 uuid: > d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 > StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: > d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 > https://github.com/pharo-project/pharo-vm.git Commit: > b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #589 > 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: /home/steven/Documents/Programmes/pharo5.0/bin [default: > /home/steven/Documents/Programmes/pharo5.0/bin/] > > > Le ven. 7 avr. 2017 Ã 12:54, Alistair Grant <akgrant0710(a)gmail.com> a > Ã©crit : > > Hi Steven, > > Can you tell us which platform you're on, and the output of pharo --version > > Cheers, > Alistair > > > On 7 Apr. 2017 12:48, "Steven RÃ©mot" <steven.remot(a)gmail.com> wrote: > > Hello everyone, > > I'm new to pharo, and was writing a simple 2D game with Athens for > rendering to practice a bit. I'm loving the environment so far, developing > the game while it's running is really enjoyable :-) . > > However, when the game is running, the pharo image will freeze at a random > time. Alt-. doesn't make my image back to normal, the only solution I found > is closing my image and opening it again, until the next freeze... > > I don't really know what to do to investigate this bug, there is no output > from pharo about this. The only thing I thought about is starting from a > fresh image, importing my code and running it again to ensure it wasn't > some messy state in the image I was using, and it froze even when running > my code from a fresh image. > > What can I do to debug it? Do you need more information to give me a > direction? > > Just in case you need it, here is the source: > https://www.dropbox.com/s/pfn7ccw27i4nqr7/Creakout-debug.st?dl=0 > > Thanks, > Steven RÃ©mot > > > >

April 8, 2017

Re: [Pharo-users] Pharo image freeze and "Alt-." has no effect

by Ben Coman

Just for starters, can you try with dev-latest VM & Image... * http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded- 201704041239-b3f27b3.zip * http://files.pharo.org/image/60/60463.zip cheers -ben On Fri, Apr 7, 2017 at 7:05 PM, Steven RÃ©mot <steven.remot(a)gmail.com> wrote: > I'm on Linux (Ubuntu 15.10), and the output of pharo -v is: > > 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] > CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 > May 4 2016 > StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: > d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 > https://github.com/pharo-project/pharo-vm.git Commit: > b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #589 > 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: /home/steven/Documents/Programmes/pharo5.0/bin [default: > /home/steven/Documents/Programmes/pharo5.0/bin/] > > > Le ven. 7 avr. 2017 Ã 12:54, Alistair Grant <akgrant0710(a)gmail.com> a > Ã©crit : > >> Hi Steven, >> >> Can you tell us which platform you're on, and the output of pharo >> --version >> >> Cheers, >> Alistair >> >> >> On 7 Apr. 2017 12:48, "Steven RÃ©mot" <steven.remot(a)gmail.com> wrote: >> >> Hello everyone, >> >> I'm new to pharo, and was writing a simple 2D game with Athens for >> rendering to practice a bit. I'm loving the environment so far, developing >> the game while it's running is really enjoyable :-) . >> >> However, when the game is running, the pharo image will freeze at a >> random time. Alt-. doesn't make my image back to normal, the only solution >> I found is closing my image and opening it again, until the next freeze... >> >> I don't really know what to do to investigate this bug, there is no >> output from pharo about this. The only thing I thought about is starting >> from a fresh image, importing my code and running it again to ensure it >> wasn't some messy state in the image I was using, and it froze even when >> running my code from a fresh image. >> >> What can I do to debug it? Do you need more information to give me a >> direction? >> >> Just in case you need it, here is the source: >> https://www.dropbox.com/s/pfn7ccw27i4nqr7/Creakout-debug.st?dl=0 >> >> Thanks, >> Steven RÃ©mot >> >> >>

April 8, 2017

Re: [Pharo-users] FileReference / and parent

by Alistair Grant

On Fri, Apr 07, 2017 at 08:43:50PM +0200, Esteban Lorenzano wrote: > > > On 7 Apr 2017, at 20:30, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Dennis, > > > > On Fri, Apr 07, 2017 at 10:58:57AM +0200, Denis Kudriashov wrote: > >> Hi Alistair. > >> > >> Do you open the issue? > >> I found that it was already exist. Look at 13217 > >> <https://pharo.fogbugz.com/f/cases/13217/FS-basename-with-compound-path-stri…> > > > > I haven't opened it yet - as you suggested in the issue, given how busy > > Esteban and everyone is with getting Pharo 6 out the door, I'm waiting > > for Pharo 7 dev to start. I've got the code and automated tests done, > > although reading the issue has made me think that I should also review > > the class comments. > > > > I'll add a comment to the issue and then submit the patch once the Pharo > > 7 inbox is open. > > that's very good... thank you very much! > > Esteban And of course, just after posting the proposed patch in the issue, I found a bug with it. After re-reading the Path class comment I've also realised that my patch breaks the explicit behaviour in the comment. But... The class comment in Path (I belive) is wrong. The class comment states that a slash (/) can be included in the file name with "parent\/child\/", however it didn't work when I tried it, and there are multiple answers in stackoverflow and stackexchange stating that / and \0 (null character) are the two forbidden (ascii) characters on linux. Windows includes / (slash), \ (backslash) and several others. Wikipedia has an article on it: https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words >From a purely practical point of view, I think trying to be completely general (meaning allowing the directory separator in a filename) in this case causes many more problems with unexpected behaviour than it solves, so I still would like to see this changed in Pharo 7 (once I fix my patch and extend the automated tests :-)). Cheers, Alistair

April 7, 2017

Re: [Pharo-users] Pharo image freeze and "Alt-." has no effect

by Steven RÃ©mot

I think I got rid of the freeze by removing my implementation of layoutChanged in my morph: CreakoutMorph>>layoutChanged super layoutChanged. surface := AthensCairoSurface extent: self extent. I used it to always have a surface that fits my morph whenever it's resized. I can totally live without it, but I'm really curious to know what makes this code freeze my image sometimes, if ever someone knows it! Le ven. 7 avr. 2017 Ã 13:05, Steven RÃ©mot <steven.remot(a)gmail.com> a Ã©crit : > I'm on Linux (Ubuntu 15.10), and the output of pharo -v is: > > 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] > CoInterpreter VMMaker.oscog-eem.1855 uuid: > d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 > StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: > d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 > https://github.com/pharo-project/pharo-vm.git Commit: > b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #589 > 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: /home/steven/Documents/Programmes/pharo5.0/bin [default: > /home/steven/Documents/Programmes/pharo5.0/bin/] > > > Le ven. 7 avr. 2017 Ã 12:54, Alistair Grant <akgrant0710(a)gmail.com> a > Ã©crit : > > Hi Steven, > > Can you tell us which platform you're on, and the output of pharo --version > > Cheers, > Alistair > > > On 7 Apr. 2017 12:48, "Steven RÃ©mot" <steven.remot(a)gmail.com> wrote: > > Hello everyone, > > I'm new to pharo, and was writing a simple 2D game with Athens for > rendering to practice a bit. I'm loving the environment so far, developing > the game while it's running is really enjoyable :-) . > > However, when the game is running, the pharo image will freeze at a random > time. Alt-. doesn't make my image back to normal, the only solution I found > is closing my image and opening it again, until the next freeze... > > I don't really know what to do to investigate this bug, there is no output > from pharo about this. The only thing I thought about is starting from a > fresh image, importing my code and running it again to ensure it wasn't > some messy state in the image I was using, and it froze even when running > my code from a fresh image. > > What can I do to debug it? Do you need more information to give me a > direction? > > Just in case you need it, here is the source: > https://www.dropbox.com/s/pfn7ccw27i4nqr7/Creakout-debug.st?dl=0 > > Thanks, > Steven RÃ©mot > > >

April 7, 2017

Re: [Pharo-users] FileReference / and parent

by Esteban Lorenzano

> On 7 Apr 2017, at 20:30, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Dennis, > > On Fri, Apr 07, 2017 at 10:58:57AM +0200, Denis Kudriashov wrote: >> Hi Alistair. >> >> Do you open the issue? >> I found that it was already exist. Look at 13217 >> <https://pharo.fogbugz.com/f/cases/13217/FS-basename-with-compound-path-stri…> > > I haven't opened it yet - as you suggested in the issue, given how busy > Esteban and everyone is with getting Pharo 6 out the door, I'm waiting > for Pharo 7 dev to start. I've got the code and automated tests done, > although reading the issue has made me think that I should also review > the class comments. > > I'll add a comment to the issue and then submit the patch once the Pharo > 7 inbox is open. thatâs very goodâ¦ thank you very much! Esteban > > Thanks for letting me know about this. > > Cheers, > Alistair > > > > >> 2017-04-04 16:59 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: >> >>> Hi Stef, >>> >>> On Tue, Apr 04, 2017 at 04:33:56PM +0200, Stephane Ducasse wrote: >>>> Hi alistair >>>> >>>> We should target Pharo 70. >>> >>> Yep, I saw Esteban's message saying he hopes 6.0 is only a week away, so >>> this can definitely wait. >>> >>> >>>> Now it is great that you help improving the file frameworks. >>>> Could you open a bug entry? >>> >>> Yep, I was just waiting to see if there was lots of resistance to these >>> changes (which there doesn't seem to be). >>> >>> >>>> Do you have tests? >>> >>> I was working on them when this email arrived. :-) >>> >>> I expect it will take me a week to get them to the point I'm happy (this >>> is a part time hobby), but they'll definitely be part of the slice / >>> pull request when I submit it. >>> >>> Cheers, >>> Alistair >>> >>> >>>> >>>> Stef >>>> >>>> On Mon, Apr 3, 2017 at 2:04 PM, Alistair Grant <akgrant0710(a)gmail.com> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I previously suggested a change to Path>>/ which actually covered two >>>>> issues: >>>>> >>>>> 1. The handling of the parent directory notation, i.e. ".." >>>>> 2. The construction of path segments when appending a string. >>>>> >>>>> As Damien pointed out, the first issue needs a bit more consideration. >>>>> >>>>> I think the second point is still problematic and can be addressed >>>>> separately. In particular: >>>>> >>>>> ('/a/b/c' asFileReference / 'd/e/f') parent "File @ /a/b/c" >>>>> >>>>> I would expect the result to be "File @ /a/b/c/d/e" >>>>> >>>>> The fix is straightforward (although someone may be able to propose a >>>>> more elgant solution): >>>>> >>>>> -- >>>>> / aString >>>>> | path additionalPath index | >>>>> >>>>> aString isEmptyOrNil >>>>> ifTrue: [ Error signal: 'Path element cannot be empty >>> or >>>>> nil']. >>>>> >>>>> additionalPath := Path from: aString. >>>>> path := self class new: self size + additionalPath size. >>>>> path copyFrom: self. >>>>> index := self size + 1. >>>>> additionalPath do: [ :each | >>>>> path at: index put: each. >>>>> index := index + 1. >>>>> ]. >>>>> ^ path >>>>> -- >>>>> >>>>> 1. Do you agree with the proposed change? >>>>> 2. (Assuming you agree): Should we target Pharo 6.0 or 7.0? >>>>> On one side, this is clearly a bug, on the other, no one has >>> reported >>>>> it to date, so it isn't having a big impact. >>>>> >>>>> Thanks, >>>>> Alistair >>>>> >>>>> >>> >>> >

April 7, 2017

Re: [Pharo-users] FileReference / and parent

by Alistair Grant

Hi Dennis, On Fri, Apr 07, 2017 at 10:58:57AM +0200, Denis Kudriashov wrote: > Hi Alistair. > > Do you open the issue? > I found that it was already exist. Look at 13217 > <https://pharo.fogbugz.com/f/cases/13217/FS-basename-with-compound-path-stri…> I haven't opened it yet - as you suggested in the issue, given how busy Esteban and everyone is with getting Pharo 6 out the door, I'm waiting for Pharo 7 dev to start. I've got the code and automated tests done, although reading the issue has made me think that I should also review the class comments. I'll add a comment to the issue and then submit the patch once the Pharo 7 inbox is open. Thanks for letting me know about this. Cheers, Alistair > 2017-04-04 16:59 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > > > Hi Stef, > > > > On Tue, Apr 04, 2017 at 04:33:56PM +0200, Stephane Ducasse wrote: > > > Hi alistair > > > > > > We should target Pharo 70. > > > > Yep, I saw Esteban's message saying he hopes 6.0 is only a week away, so > > this can definitely wait. > > > > > > > Now it is great that you help improving the file frameworks. > > > Could you open a bug entry? > > > > Yep, I was just waiting to see if there was lots of resistance to these > > changes (which there doesn't seem to be). > > > > > > > Do you have tests? > > > > I was working on them when this email arrived. :-) > > > > I expect it will take me a week to get them to the point I'm happy (this > > is a part time hobby), but they'll definitely be part of the slice / > > pull request when I submit it. > > > > Cheers, > > Alistair > > > > > > > > > > Stef > > > > > > On Mon, Apr 3, 2017 at 2:04 PM, Alistair Grant <akgrant0710(a)gmail.com> > > > wrote: > > > > > > > Hi All, > > > > > > > > I previously suggested a change to Path>>/ which actually covered two > > > > issues: > > > > > > > > 1. The handling of the parent directory notation, i.e. ".." > > > > 2. The construction of path segments when appending a string. > > > > > > > > As Damien pointed out, the first issue needs a bit more consideration. > > > > > > > > I think the second point is still problematic and can be addressed > > > > separately. In particular: > > > > > > > > ('/a/b/c' asFileReference / 'd/e/f') parent "File @ /a/b/c" > > > > > > > > I would expect the result to be "File @ /a/b/c/d/e" > > > > > > > > The fix is straightforward (although someone may be able to propose a > > > > more elgant solution): > > > > > > > > -- > > > > / aString > > > > | path additionalPath index | > > > > > > > > aString isEmptyOrNil > > > > ifTrue: [ Error signal: 'Path element cannot be empty > > or > > > > nil']. > > > > > > > > additionalPath := Path from: aString. > > > > path := self class new: self size + additionalPath size. > > > > path copyFrom: self. > > > > index := self size + 1. > > > > additionalPath do: [ :each | > > > > path at: index put: each. > > > > index := index + 1. > > > > ]. > > > > ^ path > > > > -- > > > > > > > > 1. Do you agree with the proposed change? > > > > 2. (Assuming you agree): Should we target Pharo 6.0 or 7.0? > > > > On one side, this is clearly a bug, on the other, no one has > > reported > > > > it to date, so it isn't having a big impact. > > > > > > > > Thanks, > > > > Alistair > > > > > > > > > > > >

April 7, 2017

Re: [Pharo-users] Adding our local hackerspace to Pharo Teachers page

by Offray Vladimir Luna CÃ¡rdenas

Thanks, Offray On 07/04/17 11:15, marcus.denker(a)inrira.fr wrote: > Hi, I added it to > > http://pharo.org/Teachers > > -- > Marcus Denker -- denker(a)acm.org <mailto:denker@acm.org> > http://www.marcusdenker.de > >> On 7 Apr 2017, at 17:55, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: >> >>> HackBo, Hackerspace en BogotÃ¡, Colombia.http://hackbo.co/ >

April 7, 2017

Re: [Pharo-users] using UFFI in non-crashing way

by Dimitris Chloupis

Do you guys received my CPU exceptions solution message ? Because the issue you described is already resolved by hardware. Simple and elegant solution too On Fri, 7 Apr 2017 at 11:03, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-04-07 8:22 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > But then the problem is on "how to not lose your code", not in FFI... > > > Restarting image is a problem. For any other "smalltalk" problems we got > suitable debugger but not in that case. > > > Also when image crashed we need to recover all objects state for the > script which produce crash > > > FFI is a border. > Once you start working with it, you are in C world. > And C world is nasty, hard and cumbersome. > > > Yes. And my remark was about possibility to catch C error to prevent image > crash, why it will make FFI less hard. >

April 7, 2017