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

Re: [Pharo-dev] Ask HN: Examples of elegant, non-trivial Smalltalk? | Hacker News

by Thierry Goubier

Le 29/07/2016 Ã 21:18, stepharo a Ã©crit : > Thierry > > I started a Smacc chapter in the PharoInProgress book. Ok. I'll have a look if I can contribute during my holidays... Thierry > > Stef > > > Le 29/7/16 Ã 15:56, Thierry Goubier a Ã©crit : >> >> >> 2016-07-29 15:32 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu>>: >> >> >> > On 29 Jul 2016, at 14:23, Thierry Goubier >> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> > >> > Hi Sven, >> > >> > I'd put RB + SmaCC among the lot. But I consider that really >> non-trivial : the pattern language of RB (and the underlying >> pattern matching and unification algorithm) is top notch, and how >> SmaCC builds on RB to virtually generate code / optimise code / >> then compile is nothing short of amazing. >> > >> > SmaCC comes with a pattern matching/unification algorithm over >> ASTs + auto-generation of AST code + visitor + tree equality + the >> equivalent of Flex/Bison(*) + a GUI in 11401 lines of code. >> >> Well, you don't need to convince me that there is some really >> magic code out there, thanks for pointing this out. People should >> really do more effort to promote the stuff they like, by writing >> some nice accessible article about it. (Hint, hint). >> >> >> Understood :) >> >> >> The problem is that even though Smalltalk itself is simple, the >> whole environment, being super dynamic/flexible, is not. It scares >> a lot of people that they cannot really grab and hold the code. It >> is only once you get beyond that initial hurdle (which also >> requires you to unlearn/learn a new approach), that you can start >> to explore and appreciate all the good stuff. I am still not sure >> how we can make this clear to newcomers, but it feels like a >> critical step. >> >> >> Maybe there is a question of coding style coupled with the tools? >> >> Thierry >> >> >> >> > Thierry >> > >> > (*) And a true equivalent, with LR, LALR and GLR ! >> > >> > 2016-07-29 14:05 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu>>: >> > <Social Media Marketing> >> > >> > The following interesting question/thread could use some more >> comments/votes: >> > >> > Ask HN: Examples of elegant, non-trivial Smalltalk? | Hacker News >> > >> > > https://news.ycombinator.com/item?id=12185892 >> <https://news.ycombinator.com/item?id=12185892> >> > >> > Sven >> > >> >> >> >

July 29, 2016

Re: [Pharo-dev] Ask HN: Examples of elegant, non-trivial Smalltalk? | Hacker News

by stepharo

Thierry I started a Smacc chapter in the PharoInProgress book. Stef Le 29/7/16 Ã 15:56, Thierry Goubier a Ã©crit : > > > 2016-07-29 15:32 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>>: > > > > On 29 Jul 2016, at 14:23, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > > > Hi Sven, > > > > I'd put RB + SmaCC among the lot. But I consider that really > non-trivial : the pattern language of RB (and the underlying > pattern matching and unification algorithm) is top notch, and how > SmaCC builds on RB to virtually generate code / optimise code / > then compile is nothing short of amazing. > > > > SmaCC comes with a pattern matching/unification algorithm over > ASTs + auto-generation of AST code + visitor + tree equality + the > equivalent of Flex/Bison(*) + a GUI in 11401 lines of code. > > Well, you don't need to convince me that there is some really > magic code out there, thanks for pointing this out. People should > really do more effort to promote the stuff they like, by writing > some nice accessible article about it. (Hint, hint). > > > Understood :) > > The problem is that even though Smalltalk itself is simple, the > whole environment, being super dynamic/flexible, is not. It scares > a lot of people that they cannot really grab and hold the code. It > is only once you get beyond that initial hurdle (which also > requires you to unlearn/learn a new approach), that you can start > to explore and appreciate all the good stuff. I am still not sure > how we can make this clear to newcomers, but it feels like a > critical step. > > > Maybe there is a question of coding style coupled with the tools? > > Thierry > > > > Thierry > > > > (*) And a true equivalent, with LR, LALR and GLR ! > > > > 2016-07-29 14:05 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>>: > > <Social Media Marketing> > > > > The following interesting question/thread could use some more > comments/votes: > > > > Ask HN: Examples of elegant, non-trivial Smalltalk? | Hacker News > > > > > https://news.ycombinator.com/item?id=12185892 > <https://news.ycombinator.com/item?id=12185892> > > > > Sven > > > > >

July 29, 2016

Re: [Pharo-dev] [Moose-dev] Ask HN: Examples of elegant, non-trivial Smalltalk? | Hacker News

by stepharo

Indeed. > I was at that talk, and I am not convinced that we are at that level, we are certainly not better in my opinion. The advantage that they have is the domain-specific language on top of the parsing infrastructure which makes it easy and fast to write (at least) the demos he is showing. We donât have that and his talk showed me that it is an important thing that is missing. > > -- > Does this mail seem too brief? Sorry for that, I donât mean to be rude! Please see http://emailcharter.org . > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >> On Jul 29, 2016, at 08:38, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> When I see all the buzz around languages workbenches like Rascal: >> https://www.youtube.com/watch?v=Ffx7VtEOSx4 >> >> with MOOSE+RB+SmaCC+Reflectivity+GTools we are close to these tools >> (or even better). > >

July 29, 2016

Re: [Pharo-dev] Limbo/PharoInProgress repositories

by stepharo

Hi serge these repos are mine and they have a really clear meaning: - limbo are just stekches of topics - PharoInProgress are actively written chapters - for reviews are chapters that can be taken and put in a future book. Do not worry I will not forget them. And they are important to avoid to give the impression that all the books are in messy incomplete state. You can add a readme if you want. Stef Le 29/7/16 Ã 14:55, Serge Stinckwich a Ã©crit : > Dear all, > > on SquareBracketAssociates github org, I see a Limbo repo : > https://github.com/SquareBracketAssociates/PharoLimbo > and a PharoInProgress repo: > https://github.com/SquareBracketAssociates/PharoInProgress > Basically there are collections of chapters that are not part of any > books until now. > And there is also a repo called: PharoReadyForReviews > https://github.com/SquareBracketAssociates/PharoReadyForReviews > for chapters ready for reviews but with some chapters more than 2 years old. > > Does it make sense to merge all these repos in one ? Having too much > repos, we forget about the others ... > > BTW, I add a draft of a chapter regarding Continuations (in French) I wrote > several years ago : > https://github.com/SquareBracketAssociates/PharoLimbo/blob/master/Continuat… > > Regards,

July 29, 2016

Re: [Pharo-dev] Option for as-in-moose debugger layout

by milton mamani

I agree with Yuriy stack should be in the side For me, the best way could be that you can put the widgets in the position that you want, I mean, the default layout is the vertical(stack, code, attributes) But then with the mouse click, move it to another place in the window, or put it in a new window. And have the option to save the new position by default. But this idea, can be difficult to implement 2016-07-29 12:21 GMT-04:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > > On 29 Jul 2016, at 14:41, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > On Fri, Jul 29, 2016 at 01:28:57PM +0200, Cyril Ferlicot D. wrote: > >> Le 27/07/2016 Ã 15:04, Denis Kudriashov a Ã©crit : > >>> I want it too (but I never try it). > >>> > >>> And maybe it is good time to force people taste it as default? (with > >>> setting to return classic one) > >>> > >> > >> Hi, > >> > >> At the integration it was the default but it was changed since more > >> people found the old way more convenient. > > > > Also nobody likes change, so naturally everyone complains. > > > > And itâs ok that people have different opinions. I was just asking whether > it will be hard to have the layout changeable with a setting >

July 29, 2016

Re: [Pharo-dev] segfault fresh Pharo5.0 download w/pharo VM version: 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]

by Dale Henrichs

Yesterday I reported that I was using the following script combination: ./pharo Pharo.image save xxx; ./pharo xxx.image --quit --save ./boom.st and that the MNU was being hit during the second case when I was loading boom.st and the same thing is true today, but instead of an MNU I'm getting a segFault and the execution of boom.st is not even getting a chance to start as here is stdout: foos:test> ./pharo xxx.image --quit --save ./boom.st Segmentation fault Fri Jul 29 11:12:12 2016 /export/foos1/users/dhenrich/dev/_home/dev/clients/test/pharo-vm/pharo pharo VM version: 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] Built from: CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 With: StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 And as happened yesterday saving the Pharo.image after bringing it up interactively "fixes the problem"... and skipping the `./pharo Pharo.image save xxx` avoids the problem as well .. Dale On 07/29/2016 11:04 AM, Dale Henrichs wrote: > Attached crash.dmp file ... running Ubuntu14.04 and here's a bit of > Smalltalk stack: > > 0xffb7d03c I FreeTypeFace(FT2Face)>newFaceFromExternalMemory:index: > 0xbc98a58: a(n) FreeTypeFace > 0xffb7d064 I FreeTypeFace>create 0xbc98a58: a(n) FreeTypeFace > 0xffb7d084 I FreeTypeFace>validate 0xbc98a58: a(n) FreeTypeFace > 0xffb7d0a4 I FreeTypeFont>face 0xb86ade0: a(n) FreeTypeFont > 0xffb7d0fc I > FreeTypeSubPixelAntiAliasedGlyphRenderer>renderStretchedGlyph:depth:subpixelPosition:font: > 0x9e2b218: a(n) FreeTypeSubPixelAntiAliasedGlyphRenderer > 0xffb7d130 I > FreeTypeSubPixelAntiAliasedGlyphRenderer>subGlyphOf:colorValue:mono:subpixelPosition:font: > 0x9e2b218: a(n) FreeTypeSubPixelAntiAliasedGlyphRenderer > ....snip.... > 0xbceb0b8 s WorldMorph>displayWorld > 0xbceb118 s [] in WorldState>displayWorldSafely: > 0xbceb178 s BlockClosure>on:do: > 0xbceb1d8 s BlockClosure>ifError: > 0xbceb238 s WorldState>displayWorldSafely: > 0xbceb298 s WorldState>doOneCycleNowFor: > 0xbceb2f8 s WorldState>doOneCycleFor: > 0xbceb358 s WorldMorph>doOneCycle > 0xb95ca30 s [] in MorphicUIManager>spawnNewProcess > 0xb767510 s [] in BlockClosure>newProcess > > > vm/image combo dowloaded yesterday launches without errors, so I don't > think it's my environment that is the source of the segfault ... > > I was doing a fresh build from a bash script and from the looks of the > last couple of lines it looks like that there are new changes in this > image from yesterday: > > "Postscript: > Leave the line above, and replace the rest of this comment by a useful > one. > Executable statements should follow this comment, and should > be separated by periods, with no exclamation points (!!). > Be sure to put any further comments in double-quotes, like this one." > > |repository| > repository := MCHttpRepository > location: 'http://smalltalkhub.com/mc/Pharo/Pharo50/main' > user: '' > password: ''. > (repository > loadVersionFromFileNamed:'ScriptLoader50-EstebanLorenzano.975.mcz') load. > ScriptLoader new update50761. > ! > > ----End fileIn----! > > ----QUIT----2016-07-29T12:18:23.980837+02:00 Pharo.image priorSource: > 215270! > > ----QUIT----2016-07-29T12:18:29.473484+02:00 Pharo.image priorSource: > 234661! > > If you look at the bottom of the stack you will notice that > WorldState>doOneCycle is being called and that's suspiciously similar > to the issue I reported yesterday[1] ... but a segfault this time > instead of an MNU.. > > I will go through the drill of trying to see which part of the script > is hitting this problem and provide more info ... > > It would be nice to get a clean build sooner rather than later :) > > Dale > > [1] https://pharo.fogbugz.com/f/cases/18706#BugEvent.170987

July 29, 2016

segfault fresh Pharo5.0 download w/pharo VM version: 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]

by Dale Henrichs

Attached crash.dmp file ... running Ubuntu14.04 and here's a bit of Smalltalk stack: 0xffb7d03c I FreeTypeFace(FT2Face)>newFaceFromExternalMemory:index: 0xbc98a58: a(n) FreeTypeFace 0xffb7d064 I FreeTypeFace>create 0xbc98a58: a(n) FreeTypeFace 0xffb7d084 I FreeTypeFace>validate 0xbc98a58: a(n) FreeTypeFace 0xffb7d0a4 I FreeTypeFont>face 0xb86ade0: a(n) FreeTypeFont 0xffb7d0fc I FreeTypeSubPixelAntiAliasedGlyphRenderer>renderStretchedGlyph:depth:subpixelPosition:font: 0x9e2b218: a(n) FreeTypeSubPixelAntiAliasedGlyphRenderer 0xffb7d130 I FreeTypeSubPixelAntiAliasedGlyphRenderer>subGlyphOf:colorValue:mono:subpixelPosition:font: 0x9e2b218: a(n) FreeTypeSubPixelAntiAliasedGlyphRenderer ....snip.... 0xbceb0b8 s WorldMorph>displayWorld 0xbceb118 s [] in WorldState>displayWorldSafely: 0xbceb178 s BlockClosure>on:do: 0xbceb1d8 s BlockClosure>ifError: 0xbceb238 s WorldState>displayWorldSafely: 0xbceb298 s WorldState>doOneCycleNowFor: 0xbceb2f8 s WorldState>doOneCycleFor: 0xbceb358 s WorldMorph>doOneCycle 0xb95ca30 s [] in MorphicUIManager>spawnNewProcess 0xb767510 s [] in BlockClosure>newProcess vm/image combo dowloaded yesterday launches without errors, so I don't think it's my environment that is the source of the segfault ... I was doing a fresh build from a bash script and from the looks of the last couple of lines it looks like that there are new changes in this image from yesterday: "Postscript: Leave the line above, and replace the rest of this comment by a useful one. Executable statements should follow this comment, and should be separated by periods, with no exclamation points (!!). Be sure to put any further comments in double-quotes, like this one." |repository| repository := MCHttpRepository location: 'http://smalltalkhub.com/mc/Pharo/Pharo50/main' user: '' password: ''. (repository loadVersionFromFileNamed:'ScriptLoader50-EstebanLorenzano.975.mcz') load. ScriptLoader new update50761. ! ----End fileIn----! ----QUIT----2016-07-29T12:18:23.980837+02:00 Pharo.image priorSource: 215270! ----QUIT----2016-07-29T12:18:29.473484+02:00 Pharo.image priorSource: 234661! If you look at the bottom of the stack you will notice that WorldState>doOneCycle is being called and that's suspiciously similar to the issue I reported yesterday[1] ... but a segfault this time instead of an MNU.. I will go through the drill of trying to see which part of the script is hitting this problem and provide more info ... It would be nice to get a clean build sooner rather than later :) Dale [1] https://pharo.fogbugz.com/f/cases/18706#BugEvent.170987

July 29, 2016

Re: [Pharo-dev] Option for as-in-moose debugger layout

by Yuriy Tymchuk

> On 29 Jul 2016, at 14:41, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Fri, Jul 29, 2016 at 01:28:57PM +0200, Cyril Ferlicot D. wrote: >> Le 27/07/2016 Ã 15:04, Denis Kudriashov a Ã©crit : >>> I want it too (but I never try it). >>> >>> And maybe it is good time to force people taste it as default? (with >>> setting to return classic one) >>> >> >> Hi, >> >> At the integration it was the default but it was changed since more >> people found the old way more convenient. > > Also nobody likes change, so naturally everyone complains. > And itâs ok that people have different opinions. I was just asking whether it will be hard to have the layout changeable with a setting

July 29, 2016

Regular expression to match URIs

by Casimiro - GMAIL

If someone is in need to parse URIs, then the following regex handle it: | regStr regex | regStr := '((([a-z]\w+\:)', "Match URL protocol and colon" '(/|//|///|[A-Za-z0-9%]))', "Match 1-3 slashes or single letter or digit or %" '|', "or" '(((www\d)|(www\d\d)|(www\d\d\d))[.])', "match www ou www[1-999] followed by ." '|', "or" '([A-Za-z0-9._\-]+[.]([a-z][a-z]|[a-z][a-z][a-z]|[a-z][a-z][a-z][a-z])/))', "domain name" '(([^\s()<>]+', "run of non-space, non ()<>" '|', "or" '\(([^\s()<>]+|(\([^\s()<>]+\)))*\))+)', "balanced parens up to two levels" '(\(([^\s()<>]+|(\([^\s()<>]+\)))*\)', "end with balanced aprens up to 2 levels" '|', "or" '[^\s`!()[]{};:''".,<>?Â«Â»ââââ])'. "not a space or one of these punct chars" regex := RxMatcher forString: regStr. -- The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions. == This email may be signed using PGP key *ID: 0x4134A417*

July 29, 2016

Re: [Pharo-dev] Ask HN: Examples of elegant, non-trivial Smalltalk? | Hacker News

by Serge Stinckwich

On Fri, Jul 29, 2016 at 3:32 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 29 Jul 2016, at 14:23, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Hi Sven, >> >> I'd put RB + SmaCC among the lot. But I consider that really non-trivial : the pattern language of RB (and the underlying pattern matching and unification algorithm) is top notch, and how SmaCC builds on RB to virtually generate code / optimise code / then compile is nothing short of amazing. >> >> SmaCC comes with a pattern matching/unification algorithm over ASTs + auto-generation of AST code + visitor + tree equality + the equivalent of Flex/Bison(*) + a GUI in 11401 lines of code. > > Well, you don't need to convince me that there is some really magic code out there, thanks for pointing this out. People should really do more effort to promote the stuff they like, by writing some nice accessible article about it. (Hint, hint). > > The problem is that even though Smalltalk itself is simple, the whole environment, being super dynamic/flexible, is not. It scares a lot of people that they cannot really grab and hold the code. It is only once you get beyond that initial hurdle (which also requires you to unlearn/learn a new approach), that you can start to explore and appreciate all the good stuff. I am still not sure how we can make this clear to newcomers, but it feels like a critical step. There is an initial tutorial that needs some love here: https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Smacc -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

July 29, 2016