- Pharo-users - lists.pharo.org

Re: [Pharo-users] anotations like <todo> etc.

by Marcus Denker

> On 1 Jun 2017, at 10:39, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-05-31 19:48 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > the pragma is less intromission with code, but it has to be put in a specific place. > > I think Marcus with Ronie extended pragmas to bind them to AST-nodes. It was needed for lowcode if I remember correctly. Maybe we can add it in Pharo 7? It would be nice to revisit this directionâ¦ we had a number of designs (the one Ronie did was the third oneâ¦ for 3 different projectsâ¦) In addition, we should explore pragmas for variable definitions on the class level. I will add this to my list of things to explore for pharo 7. Marcus

June 1, 2017

Re: [Pharo-users] anotations like <todo> etc.

by Denis Kudriashov

2017-06-01 10:36 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > In fact it is not something new. You always able put any flag as pragma or > message in your methods to easily find them later. For example you can put > <issue: 'this method is not working when arg = 5'>. Then you can find it in > spotter by tapping "issue:". > With Calypso we can implement special method group "todo" and also class > group to show classes which methods has this flag > I add issue for this Implement method and class groups for #todo <https://github.com/dionisiydk/Calypso/issues/56>

June 1, 2017

Re: [Pharo-users] anotations like <todo> etc.

by Denis Kudriashov

2017-05-31 19:48 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > the pragma is less intromission with code, but it has to be put in a > specific place. I think Marcus with Ronie extended pragmas to bind them to AST-nodes. It was needed for lowcode if I remember correctly. Maybe we can add it in Pharo 7?

June 1, 2017

Re: [Pharo-users] anotations like <todo> etc.

by Denis Kudriashov

2017-05-31 19:19 GMT+02:00 Petr Fischer <petr.fischer(a)me.com>: > Hello, in Pharo 6.0, there is new annotations/pragmas like "<todo>". > > Is there any doc about this? How can I browse all "todos", how can I > browse all possible annotations etc.? > In fact it is not something new. You always able put any flag as pragma or message in your methods to easily find them later. For example you can put <issue: 'this method is not working when arg = 5'>. Then you can find it in spotter by tapping "issue:". With Calypso we can implement special method group "todo" and also class group to show classes which methods has this flag

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by Denis Kudriashov

2017-06-01 10:20 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-05-31 17:57 GMT+02:00 horrido <horrido.hobbies(a)gmail.com>: > >> I'm using Pharo 5.0 > > > I test it with Pharo 6 (latest image and VM) and have no problem. Could > you check it too? (I tested it on MAC)

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by Denis Kudriashov

2017-05-31 17:57 GMT+02:00 horrido <horrido.hobbies(a)gmail.com>: > I'm using Pharo 5.0 I test it with Pharo 6 (latest image and VM) and have no problem. Could you check it too?

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by Guillermo Polito

Horrido, Can you also provide the stack associated with the segmentation fault? Usually the VM captures the signal and dumps the current stack at the moment of the crash in stdout. You'll find the same stack in the file crash.dmp. On Thu, Jun 1, 2017 at 6:51 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Wed, May 31, 2017 at 10:23 PM, horrido <horrido.hobbies(a)gmail.com> > wrote: > >> I have a puzzling bug. I've narrowed the scenario down to this code: >> >> CrankyÂ»initA >> a := ((StringMorph contents: '####') color: Color white) position: (0@0 >> ). >> m addMorph: a >> >> CrankyÂ»initialize >> f := Form fromFileNamed: 'hot_air_balloon_mysticmorning.jpg'. >> m := ImageMorph new. >> m form: f. >> self initA. >> m openInWindowLabeled: 'Cranky'. >> delay := (Delay forSeconds: 5). >> [ [ true ] whileTrue: [ a contents: 0 asString. delay wait ] fork >> >> I can run this application for hours and hours with no problem. However, >> if >> I run it for a while and then close the application and then save/exit the >> image, the next time I start the image, there is some likelihood it will >> crash dump. The probability is something like 5-10%. >> >> Interestingly, if I remove the statement... >> >> a contents: 0 asString. >> >> from the infinite loop, I've not been able to replicate the crash. Is >> there >> something wrong with the way I'm updating the contents of the StringMorph? >> > > Can you try a few other variations... > [ [ true ] whileTrue: [ 0 asString. delay wait ] fork. > [ [ true ] whileTrue: [ a contents: '0'. delay wait ] fork. > [ [ true ] whileTrue: [ a contents: '0'. ] forkAt: 20. > > cheers -ben > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by Ben Coman

On Wed, May 31, 2017 at 10:23 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > I have a puzzling bug. I've narrowed the scenario down to this code: > > CrankyÂ»initA > a := ((StringMorph contents: '####') color: Color white) position: (0@0 > ). > m addMorph: a > > CrankyÂ»initialize > f := Form fromFileNamed: 'hot_air_balloon_mysticmorning.jpg'. > m := ImageMorph new. > m form: f. > self initA. > m openInWindowLabeled: 'Cranky'. > delay := (Delay forSeconds: 5). > [ [ true ] whileTrue: [ a contents: 0 asString. delay wait ] fork > > I can run this application for hours and hours with no problem. However, if > I run it for a while and then close the application and then save/exit the > image, the next time I start the image, there is some likelihood it will > crash dump. The probability is something like 5-10%. > > Interestingly, if I remove the statement... > > a contents: 0 asString. > > from the infinite loop, I've not been able to replicate the crash. Is there > something wrong with the way I'm updating the contents of the StringMorph? > Can you try a few other variations... [ [ true ] whileTrue: [ 0 asString. delay wait ] fork. [ [ true ] whileTrue: [ a contents: '0'. delay wait ] fork. [ [ true ] whileTrue: [ a contents: '0'. ] forkAt: 20. cheers -ben

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by horrido

Thanks, Hilaire. I had high hopes for your suggestion. But after testing a few times, Pharo crashed again. So the step protocol doesn't solve the problem, either. HilaireFernandes wrote > Alternatively use the step protocol of the Morph class. I think it is > documented in the Pharo by example book. > > Hilaire > > > Le 31/05/2017 Ã 17:00, Denis Kudriashov a Ã©crit : >> Hi Horrido. >> >> Morphic is not thread safe library. Users should not update morphs >> state directly from background processes. Use #defer: message to >> update morphs in such cases. >> Try following loop: >> >> [ [ true ] whileTrue: [ UIManager default defer: [ a contents: 0 >> asString]. delay wait ] fork >> >> > > -- > Dr. Geo > http://drgeo.eu -- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948774.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 31, 2017

Re: [Pharo-users] ANTLR4 to SmaCC

by Henrique Rocha

Thierry Goubier wrote > LL(*) brings itself to entirely different hacks to play with the tokens > and lexical analysis that LR() grammars, and most of the hard work on > parsers is in that area. > > I haven't looked if the reversed recursion in ANTLR is hard to convert. I agree. But I have seem some tricks and tips to convert one kind to the other. It seems like a lot of the work can be automated. Thierry Goubier wrote > Write a ANTLRv4 grammar syntax grammar in SmaCC would do the trick. Unfortunately, I dont have the skills or the knowledge in SmaCC to write this in SmaCC. I tried and failed (so many times) to convert a specific language to SmaCC and I got nowhere (I cant even imagine to do a more generic syntax grammar such as ANTLR). That is why I am asking for help if anyone else has done something like that. Thanks and best regards, - Henrique -- View this message in context: http://forum.world.st/ANTLR4-to-SmaCC-tp4948738p4948771.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 31, 2017