- Pharo-dev - lists.pharo.org

New CogVMs available

by Eliot Miranda

at http://www.mirandabanda.org/files/Cog/VM/VM.r3350/. CogVM binaries as per VMMaker.oscog-eem.1315/r3350 General: Make the bounds check in primitiveObject:perform:... more restrictive and fix bugs in the commentary. Make stack pages a reasonable size. My math was wrong and the size was half as big as intended. Extend the fastPrimTrace scheme to trace stack overflow, prim failure and prim retry to help debug the phantom stack frame bug in Cog Spur. Cogit: Fix old bug in ceMNUFromPICMNUMethod:receiver: that has been masked by cacheing of MNU method in MNU PIC entries. ceMNUFromPICMNUMethod:receiver: must set up lkupClass before calling handleMNU:... Revamp icache flushing in the Cogit for ARM. Move icache flush for generated methods/pics to the fillIn*Header: routines. Make sure the cache is flushed in generateCaptureCStackPointers:. Flush the entire PIC when extending it. Fix ARM-only regression in StackToRegisterMappingCogit's PIC aborts when the SimpleStackBasedCogit was fixed. Make ARM rotated 8bit constants actually be correct(er) ie 16r4000001 (SmallInteger 16r2000000) work. Spur: Fix ceActivateFailingPrimitiveMethod: to return properly after retrying a primitive after checkForAndFollowForwardedPrimitiveState. e.g. fixes | s | 1 to: 5 do: [:i| s := 'bar'. s becomeForward: 'bzzt' copy. 'foo' <= s] Fix bug in followForwardedFrameContents:stackPointer: so that arguments are actually followed. N.B. drives the above bug underground ;-). so that named constants (defines) are not elided. Make accessor depth calculation more accurate by not considering fetchInteger:ofObject: and arraySize: et al as object accessors. Newspeak: Remove landmine left from restructing implicit receiver and outer sends as clean sends. Slang: Do a more thorough job of transforming complex to:[by:]do: loops so that the limit expression is only evaluated once, not on each iteration of the loop. Make the read-before-written initializer safer, only initialzing simple types. Plugins: Regenerated because of changes in accessorDepth calculation, constant elimination, and read-before-use initialization. -- best, Eliot

May 19, 2015

Re: [Pharo-dev] Manifest class values - instance or class side

by Kasper Osterbye

Sergio Fedi wrote >> >> Case created: >> >> >> https://pharo.fogbugz.com/f/cases/15557/New-PackageManifests-should-be-clas… >> > > Case Resolved (Review needed) It is scary, but all pharo unittests succeed with either implementation :-( -- View this message in context: http://forum.world.st/Manifest-class-values-instance-or-class-side-tp482644… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 19, 2015

Re: [Pharo-dev] Code generation for ASTs with syntax errors

by Ben Coman

On Wed, May 13, 2015 at 4:41 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > On 13 May 2015 at 08:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Only three methods are needed to allow generating executable methods from >> such an AST: the SyntaxErrorNotification >> is raised at runtime instead of compile time. >> > > What is the advantage of allowing syntax errors into the running system, when they can be trapped statically before that ? It seems to me the advantage of this change is that it allows compilation to complete rather than bombing out part way through. But just because compilation finishes, doesn't mean it needs to be committed into the runtime system. > Syntax errors shouldn't require immediate fixing during compilation per > se, but there should be a way to deal with them "at compile time" âwhatever > that means for us. > For instance, faulty methods could have a flashy icon in the browser; I > think I'd even color the whole package-class-protocol-selector in red if > either of them contain faulty methods. > I guess it *should* mean that the faulty-compiled-method is not committed but stored in a temporary buffer similar to how editing source is effectively done in a temporary buffer. Indication of the fault would only be needed in the window that compiled the fault. cheers -ben

May 18, 2015

Re: [Pharo-dev] Main pillar web site?

by H. Hirzel

Luc, Thanks for the nice diagram showing Pillar in action. I suggest to include it on the pillar web site. And maybe you have some additional documentation. For example about the parser. --Hannes On 5/18/15, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi all, > > As a teacher, I wrote a little Lab subject to introduce the Visitor design > pattern to students using Pillar. > And I used the following fig to describe it. > > HIH, > > #Luc > > 2015-05-18 20:16 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > >> Thank you. >> >> Is it possible to add a short paragraph about the >> >> Rational >> >> for Pillar? >> >> It seems to be a text format for the PRnnn classes which is easy to >> parse. >> >> Which formats does the Pillar documentation tool chain read and which >> ones are generated? >> >> --Hannes >> >> On 5/4/15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> > Hi. >> > The documentation is now here: >> > >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> > >> > We're still updating the documentation so that still can change. >> > >> > On 4 May 2015 at 16:14, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> Thank you! >> >> >> >> Here is the summary >> >> >> >> >> >> >> >> Pillar documentation >> >> ==================== >> >> >> >> Start page >> >> http://www.smalltalkhub.com/#!/~Pier/Pillar >> >> >> >> >> >> Documentation >> >> https://github.com/pillar-markup/pillar-documentation >> >> >> >> >> >> >> >> First Google hit >> >> >> https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/… >> >> >> >> Leads to Pharo contribution CI server (Confirm security exception, it >> is >> >> safe). >> >> >> >> >> >> >> >> Pillar tool chain repositories >> >> ------------------------------- >> >> >> >> https://github.com/pillar-markup >> >> >> > >> > >> > >> > -- >> > Cheers >> > Cyril Ferlicot >> > >> > >> >> >

May 18, 2015

Re: [Pharo-dev] [Moose-dev] [SURVEY] Pillar input/output files.

by Alexandre Bergel

Hi Cyril, It does not look that different. Something I may recommend, is that Pillar should be effective at writing other things than a book. So, the chapter decomposition should not be forced. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 4, 2015, at 7:38 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > I'm currently working on the way we manage the input files and the output files. > The way we manage the files now makes hard some improvement of Pillar. > That's why with Damien we though about makes some changes. The changes > are big so I wanted to talk about that with you. > We propose to have always 1 file with all the work inside. That can > use the inputFile tag. For example: > > "${inputFile:Chapter1.pillar}$ > > ${inputFile:Chapter2.pillar}$ > > ${inputFile:Chapter3.pillar}$ > > ${inputFile:Chapter4.pillar}$" > > And the option "separateOutputFiles" will now create 1 file each time > we have a new Chapter. (!Level 1 header). > That will make simpler the way to number everything and to create > anchor because those 2 doesn't work well with the "separateOutputFile" > option. > > What do you thing? That would be good with you? > > -- > Cheers > Cyril Ferlicot > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

May 18, 2015

Re: [Pharo-dev] Main pillar web site?

by Luc Fabresse

2015-05-18 21:58 GMT+02:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > Hi Luc, > I think Pillar is great to learn the visitor pattern ! Now we also > added the Transformer which use visitor too. I don't know if you saw > that. > Not yet but I will have a look at some point ;-) keep pushing, Cyril! Luc > > On 18 May 2015 at 21:25, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > Hi all, > > > > As a teacher, I wrote a little Lab subject to introduce the Visitor > design > > pattern to students using Pillar. > > And I used the following fig to describe it. > > > > HIH, > > > > #Luc > > > > 2015-05-18 20:16 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > >> > >> Thank you. > >> > >> Is it possible to add a short paragraph about the > >> > >> Rational > >> > >> for Pillar? > >> > >> It seems to be a text format for the PRnnn classes which is easy to > parse. > >> > >> Which formats does the Pillar documentation tool chain read and which > >> ones are generated? > >> > >> --Hannes > >> > >> On 5/4/15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > >> > Hi. > >> > The documentation is now here: > >> > > >> > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > >> > > >> > We're still updating the documentation so that still can change. > >> > > >> > On 4 May 2015 at 16:14, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > >> >> Thank you! > >> >> > >> >> Here is the summary > >> >> > >> >> > >> >> > >> >> Pillar documentation > >> >> ==================== > >> >> > >> >> Start page > >> >> http://www.smalltalkhub.com/#!/~Pier/Pillar > >> >> > >> >> > >> >> Documentation > >> >> https://github.com/pillar-markup/pillar-documentation > >> >> > >> >> > >> >> > >> >> First Google hit > >> >> > >> >> > https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/… > >> >> > >> >> Leads to Pharo contribution CI server (Confirm security exception, > it > >> >> is > >> >> safe). > >> >> > >> >> > >> >> > >> >> Pillar tool chain repositories > >> >> ------------------------------- > >> >> > >> >> https://github.com/pillar-markup > >> >> > >> > > >> > > >> > > >> > -- > >> > Cheers > >> > Cyril Ferlicot > >> > > >> > > >> > > > > > > -- > Cheers > Cyril Ferlicot > >

May 18, 2015

Re: [Pharo-dev] Main pillar web site?

by Cyril Ferlicot

Hi Luc, I think Pillar is great to learn the visitor pattern ! Now we also added the Transformer which use visitor too. I don't know if you saw that. On 18 May 2015 at 21:25, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi all, > > As a teacher, I wrote a little Lab subject to introduce the Visitor design > pattern to students using Pillar. > And I used the following fig to describe it. > > HIH, > > #Luc > > 2015-05-18 20:16 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: >> >> Thank you. >> >> Is it possible to add a short paragraph about the >> >> Rational >> >> for Pillar? >> >> It seems to be a text format for the PRnnn classes which is easy to parse. >> >> Which formats does the Pillar documentation tool chain read and which >> ones are generated? >> >> --Hannes >> >> On 5/4/15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> > Hi. >> > The documentation is now here: >> > >> > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> > >> > We're still updating the documentation so that still can change. >> > >> > On 4 May 2015 at 16:14, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> Thank you! >> >> >> >> Here is the summary >> >> >> >> >> >> >> >> Pillar documentation >> >> ==================== >> >> >> >> Start page >> >> http://www.smalltalkhub.com/#!/~Pier/Pillar >> >> >> >> >> >> Documentation >> >> https://github.com/pillar-markup/pillar-documentation >> >> >> >> >> >> >> >> First Google hit >> >> >> >> https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/… >> >> >> >> Leads to Pharo contribution CI server (Confirm security exception, it >> >> is >> >> safe). >> >> >> >> >> >> >> >> Pillar tool chain repositories >> >> ------------------------------- >> >> >> >> https://github.com/pillar-markup >> >> >> > >> > >> > >> > -- >> > Cheers >> > Cyril Ferlicot >> > >> > >> > -- Cheers Cyril Ferlicot

May 18, 2015

Re: [Pharo-dev] [Moose-dev] [SURVEY] Pillar input/output files.

by Cyril Ferlicot

Hi, I think we'll be able to avoid what i've expose on the first message. I changed the way Pillar parsed the files so it's not easier to create a global numerator or inter file links. When i'll have something that work i'll do a new configuration a post a message on the ML. On 18 May 2015 at 22:53, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Cyril, > > It does not look that different. Something I may recommend, is that Pillar > should be effective at writing other things than a book. So, the chapter > decomposition should not be forced. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 4, 2015, at 7:38 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > I'm currently working on the way we manage the input files and the output > files. > The way we manage the files now makes hard some improvement of Pillar. > That's why with Damien we though about makes some changes. The changes > are big so I wanted to talk about that with you. > We propose to have always 1 file with all the work inside. That can > use the inputFile tag. For example: > > "${inputFile:Chapter1.pillar}$ > > ${inputFile:Chapter2.pillar}$ > > ${inputFile:Chapter3.pillar}$ > > ${inputFile:Chapter4.pillar}$" > > And the option "separateOutputFiles" will now create 1 file each time > we have a new Chapter. (!Level 1 header). > That will make simpler the way to number everything and to create > anchor because those 2 doesn't work well with the "separateOutputFile" > option. > > What do you thing? That would be good with you? > > -- > Cheers > Cyril Ferlicot > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- Cheers Cyril Ferlicot

May 18, 2015

Re: [Pharo-dev] Code generation for ASTs with syntax errors

by Marcus Denker

> On 13 May 2015, at 10:41, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > On 13 May 2015 at 08:35, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Only three methods are needed to allow generating executable methods from such an AST: the SyntaxErrorNotification > is raised at runtime instead of compile time. > > I can hear the noise of eyebrows raising in the compiler community :) > Yes! :-) > Syntax errors shouldn't require immediate fixing during compilation per se, but there should be a way to deal with them "at compile time" âwhatever that means for us. For instance, faulty methods could have a flashy icon in the browser; I think I'd even color the whole package-class-protocol-selector in red if either of them contain faulty methods. > I think that GT does it already right: it does not insert the error message in the text, but instead shows it using a tiny window undefendend of the text. Combined with syntax highlighting, this should be very close to what we need (the devil is in the detail, of course). As for finding them: the nice property of syntax errors is that they are trivial to detect staticallyâ¦ so e.g. we can add that people never can commit code like that, and of course code critics can find it triviallyâ¦ the rule just needs to check for #isFaulty (maybe we should range that to #hasSyntaxErrors). Marcus

May 18, 2015

Re: [Pharo-dev] untypeable key combination

by Nicolai Hess

2015-05-15 9:55 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > We now use a new class for the space-key as key combination. fixed and > included in 50045 (https://pharo.fogbugz.com/default.asp?15529) > This way we don't end up with hundreds of obsolete class instances. > > But the problem with circular references still exist. > 15535 <https://pharo.fogbugz.com/default.asp?15535> > break circular reference for keymappings > > I could need some help here, any idea how to work with the key mapping > registration without holding (or how to release) strong references? > > > thanks in advance > nicolai > > Can anyone help me with this. I need a way to break the circular references. a class is referenced by its compiled method the compiled method is referenced by the method context the method context is reference by a block context (the keymapping action) the block context is referenced by the registration item the registration item is referenced by the pragma registration builder the builder is reference by the method context (it is the method argument) and here the circle closes. > > > 2015-02-20 9:26 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> >> > On 19 Feb 2015, at 10:19, Nicolai Hess <nicolaihess(a)web.de> wrote: >> > >> > Fogbugz issue 14936 >> > and slice in inbox >> > >> > After loading this slice, there are still many references to the (now) >> obsolete class KMUntypeableSingleKeyCombination. >> > I tried to remove these references with the following code : >> > >> > NECPreferences popupShowWithShortcut: nil. >> > KMSingleKeyCombination reset. >> > KMSpecialCharSingleKeyCombination reset. >> > KMRepository reset. >> > >> > >> > But they arent removed. >> > >> > Anyone knows how to re-init all users of >> KMUntypeableSingleKeyCombination ? >> > >> > >> >> Very strangeâ¦ using âexplore pointersâ with the old inspector, it shows >> lots of instancesâ¦ I sadly have no >> time to now look deeper, but the pointer explorer should be a way to find >> who holds onto themâ¦ >> >> Marcus >> >> >> >> >

May 18, 2015