- Pharo-dev - lists.pharo.org

Thank you

by Pavel Krivanek

Hi, yesterday I have seen this interesting talk: https://www.youtube.com/watch?v=VS6IpvTWwkQ&app=desktop ...where pictures like this were presented: https://image.slidesharecdn.com/iscodereviewthesolution-confraria-141101115… I would like to thank to StÃ©phane Ducasse, Esteban Lorezano, Marcus Denker, Tudor Girba and many others for their ungrateful hard work on collecting and managing funds and human resources so we are closer to the first picture. Afterwards I would like to thank to all consortium and association members as well as all the contributors for their support of our common dream - better Pharo. THANK YOU! Best regards -- Pavel

Nov. 14, 2017

UFFI/Sista/Scorch

by Ben Coman

Just curious regarding Slide 16 [1] which indicates UFFI sequence is... 1. Generate bytecodes for marshalling 2. Re-send method invocation Do the bytecodes get cached so that (1.) is only down once? What impact is Sista/Scorch expected to have on UFFI? Considering for example that the commonly used method... ffiCall: fnSpec ^ (self ffiCalloutIn: thisContext sender) convention: self ffiCallingConvention; function: fnSpec module: self ffiLibraryName ...has several message sends. [1] https://www.slideshare.net/esug/unifiedffi-a-common-language-for-the-outsid… btw, Slide 2 gave me a nice chuckle to start the day. Stabilization is a difficult/boring task with highly visible issues which Esteban bears the brunt of dealing with, along with accompanying pressures. I'd like to take this random opportunity to thank Esteban for his continuing efforts, and also previous Consortium engineers (Igor) and those supporting them. We wouldn't be where we are today without such a focal point. cheers -ben

Nov. 14, 2017

Re: [Pharo-dev] Pharo6.1 World menu order

by Pavel Krivanek

2017-11-13 21:02 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > I would remove also MC from this list. > Too many items. :) > > For Pharo 7: https://github.com/pharo-project/pharo/pull/478/files -- Pavel > Stef > > On Mon, Nov 13, 2017 at 8:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Placing it in the most used tools makes sense to me, because it really is >> used a lot. ... so maybe move it just above Monticello Browser :) >> >> > It breaks muscle memory. >> >> That's good, because you can finally liberate yourself from the bad >> memory and learn cmd+O+B instead. :-D >> >> Peter >> >> On Mon, Nov 13, 2017 at 8:37 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> I find world menu order in Pharo 6.1. with enable Iceberg a little bit >>> awkward :) >>> >>> [image: Inline images 1] >>> >>> Any thought on why Iceberg is the first? It breaks muscle memory. >>> >>> P.S. To fix the order remove `parent: #'MostUsedTools'` >>> from IceRepositoriesBrowser class>>#menuCommandOn: so that implementation >>> is: >>> >>> menuCommandOn: aBuilder >>> "Add a custom menu item to the world menu" >>> <worldMenu> >>> >>> (aBuilder item: #'Iceberg') >>> order: 0.8; >>> icon: self icon; >>> "parent: #'MostUsedTools'; <-- remove" >>> keyText: 'o, i'; >>> action: [ self open ]. >>> >>> >>> >>> Cheers, >>> Alex >>> >> >> >

Nov. 13, 2017

Re: [Pharo-dev] Publishing a book with Pillar

by Julien

> Le 13 nov. 2017 Ã 21:01, Stephane Ducasse <stepharo.self(a)gmail.com> a Ã©crit : > > Hi guys > > we are working on pillar and we will probably release a new alph version soon. > I'm updating the doc. But I found that the doc I was writing can help > some of you. > > Julien is written a nice booklet on USBdrivers and he told me that > this doc works super well on mac. > > Stef > <book.pdf> Thanks for your work on this beautiful project guys. :-) Julien

Nov. 13, 2017

Re: [Pharo-dev] Pharo6.1 World menu order

by Cyril Ferlicot D.

Le 13/11/2017 Ã 20:37, Aliaksei Syrel a Ã©critÂ : > Hi, > > I find world menu order in Pharo 6.1. with enable Iceberg a little bit > awkward :) > > Inline images 1 > > Any thought on why Iceberg is the first? It breaks muscle memory. > It is first because other items does not have any order. The order and priorities where integrated in Pharo 7 in this PR: https://github.com/pharo-project/pharo/pull/202 Since it was not backported, Iceberg is first in Pharo 7. > P.S. To fix the order remove `parent: #'MostUsedTools'` > fromÂ IceRepositoriesBrowser class>>#menuCommandOn: so that > implementation is: > > menuCommandOn: aBuilderÂ > "Add a custom menu item to the world menu" > <worldMenu>Â > > (aBuilder item: #'Iceberg') > order: 0.8;Â > icon: self icon;Â Â > "parent: #'MostUsedTools';Â Â <-- remove" > keyText: 'o, i'; > action: [ self open ]. > > > Cheers, > Alex -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Nov. 13, 2017

Re: [Pharo-dev] Publishing a book with Pillar

by Cyril Ferlicot D.

Le 13/11/2017 Ã 21:01, Stephane Ducasse a Ã©critÂ : > Hi guys > > we are working on pillar and we will probably release a new alph version soon. > I'm updating the doc. But I found that the doc I was writing can help > some of you. > Cool! Don't forget to focus a little on Windows for the next version ;D I know Guille work on that front but I wanted to add a little reminder. I would like to be able to use Pillar and I currently have only Windows for now. > Julien is written a nice booklet on USBdrivers and he told me that > this doc works super well on mac. > > Stef > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Nov. 13, 2017

Re: [Pharo-dev] [Debugger] Is "run to here" broken?

by Guillermo Polito

Yeah, Thanks Thomas :) It is cool that you're learning the inners of the debugger! On Mon, Nov 13, 2017 at 8:02 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks Thomas for this analysing. I will reread the thread carefully. > I would love to see if pharoers have other ideas and wishes to improve > our cool debugger > > Stef > > On Mon, Nov 13, 2017 at 5:23 PM, Thomas Dupriez > <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > > > > > > Le 13/11/2017 Ã 15:56, Ben Coman a Ã©crit : > > > > > > > > On Mon, Nov 13, 2017 at 9:32 PM, Thomas Dupriez > > <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > >> > >> > >> > >> Le 13/11/2017 Ã 14:08, Ben Coman a Ã©crit : > >> > >> > >> > >> On Mon, Nov 13, 2017 at 8:40 PM, Thomas Dupriez > >> <thomas.dupriez(a)ens-paris-saclay.fr> wrote: > >>> > >>> I dug a bit in this issue. Here are the results: > >>> > >>> > >>> # Problem raised by Stephanne > >>> Code like the following is open in the debugger: > >>> > >>> `myMethod > >>> 1+1. <PROGRAMCOUNTER> > >>> MyClass new myEvalBlock: [ > >>> 2+2. <CURSOR> > >>> ]. > >>> 3+3.` > >>> > >>> The program counter is on the 1+1, the cursor is at the end of the 2+2 > >>> line. > >>> Right-click, "Run to here". > >>> -> the program counter moves to the 3+3, and does not stop at the 2+2 > >>> (where the cursor is). Even though the 2+2 does get evaluated (the > >>> myEvalBlock method evaluates the blocks it receives). > >>> If there was no code after the block, the debugger would jump back to > the > >>> caller of myMethod. > >>> > >>> # Why this happens > >>> The implementation of RunToHere (source code below) is basically to > >>> stepOver until the context is different or the source code position of > the > >>> program counter is higher or equal to the source code position of the > >>> cursor/selection. > >>> > >>> Since the debugger uses stepOver, it executes myEvalBlock without > >>> stopping, reaches the 3+3 and see it has gone further than the source > code > >>> position of the cursorm so it stops. > >>> > >>> Source code of DebugSession>>#runToSelection:inContext: > >>> > >>> `runToSelection: selectionInterval inContext: aContext > >>> "Attempt to step over instructions in selectedContext until the > >>> execution reaches the selected instruction. This happens when > the > >>> program counter passes the begining of selectionInterval. > >>> > >>> A not nill and valid interval is expected." > >>> > >>> (self pcRangeForContext: aContext) first >= selectionInterval > >>> first > >>> ifTrue: [ ^self ]. > >>> self stepOver: aContext. > >>> [ aContext == self interruptedContext and: [ (self > >>> pcRangeForContext: aContext) first < selectionInterval first ] ] > >>> whileTrue: [ self stepOver: aContext ]` > >>> > >>> # Observations and thoughts > >>> - Replacing the stepOver with a stepInto -> This made the RunToHere > stops > >>> when resolving the 'new' message (because the context changes). > >> > >> > >> Thanks for looking into this Thomas. > >> What happens if you use stepThrough rather than stepInto? > >> > >> cheers -ben > >> > >> > >> Using `stepThrough: aContext` instead of `stepInto: aContext`, the > >> RunToHere in the block stops at the intended place: the 2+2. > >> Printing the sequence of `self pcRangeForContext: aContext` yields the > >> following. It doesn't show precisely the stop in the block, and instead > >> shows an interval encompassing the whole block. That's what I was using > to > >> see where the execution was going during the RunToHere loop so I guess > >> that's not a precise enough indicator for this situation... > >> (21 to: 22)(34 to: 36)(49 to: 60)(38 to: 60)(38 to: 60) > >> > >> I also tried the case where the block does not get evaluated (changing > >> myEvalBlock so that it does nothing). In this situation, the RunToHere > with > >> a stepThrough ends up at the intended place, the 3+3. > >> > >> So... just use stepThrough for the RunToHere I guess? > > > > > > Seems like expected behaviour. > > Could you create an Issue/Pull Request to provide some concrete code to > > review? > > > > Now the trick will be if you can devise some tests to go with this. > > For examples perhaps look at senders of newDebugSessionNamed:startedAt: > > including SpecDebugger>>testBasic. > > > > cheers -ben > > > > > > > > I opened an issue on FogBugz: https://pharo.fogbugz.com/f/cases/20687/ > > > > Attached are the file out of the test code (MyClass.st) and the fixed > > runToSelection:inContext: (DebugSession-runToSelectioninContext). > > I'll make a pull request tomorrow. > > > > For the test, I'm thinking about something like the following, that > checks > > the source code position of the pc after the runToSelection. (It's not > > working yet) > > Now that I think of it, the source code position of the pc will maybe be > the > > whole block (as experienced earlier) so this approach may end up not > > working. > > I'll come back to that tomorrow. > > > > Draft for a test: > > `testRunToSelectionInContext > > |context_ process_ session_| > > "The variable names have an underscore to distinguish them from those > > declared in the setUp method of this TestCase (DebuggerModelTest), which > are > > not suited for this test (because not making a debug session out of > suitable > > code)" > > context_ := [1+1. > > self evalBlock:[2+2]. > > 3+3. > > ] asContext. > > process_ := Process > > forContext: context_ > > priority: Processor userInterruptPriority. > > > > session_:= process_ newDebugSessionNamed: 'test session' startedAt: > > context_. > > session_ runToSelection: (Interval from: 28 to: 27) inContext: > context_. > > self assert: ((session_ pcRangeForContext: context_) first == 3)` > > > > cheers - Thomas > > > > > >> > >> Thomas > >> > >> > >> > >>> > >>> > >>> - Replacing the stepOver with stepInto and removing the equal condition > >>> on contexts -> The RunToHere goes to the 3+3. Looking at the source > code > >>> position of the program counter, it doesn't enter the block and seems > to > >>> resolve it in a single step. I don't really get why that is, > considering > >>> using the stepInto button of the debugger does enter the block. Here > is the > >>> series of source code positions of the program counter during the > RunToHere: > >>> (21 to: 22)(34 to: 36)(34 to: 36)(49 to: 60)(38 to: 60)(38 to: 60)(65 > to: > >>> 66). > >>> However, removing the equal condition on contexts means that if the > >>> method call returns before reaching the cursor, it won't stop! > >>> > >>> - An idea could be to have the RunToHere place a metalink on the > selected > >>> node and let the execution run until it hits the metalink, which then > >>> updates the debugger. Potential problems are that it implies > installing a > >>> metalink on a method that is already on the stack, which may not be > that > >>> easy to do properly (in particular, it affects the program counter > since it > >>> changes the bytecode), and there is the potential case where the > metalink is > >>> never reached (for example imagine the myEvalBlock: method of my > example is > >>> just storing the block and not evaluating it). > >>> > >>> > >>> Cheers, > >>> Thomas > >>> > >>> > >>> > >>> Le 09/11/2017 Ã 22:06, Stephane Ducasse a Ã©crit : > >>>> > >>>> Agreed. Thomas? It would be a good bone to ... (Un bon os a ronger) . > >>>> > >>>> Stef > >>>> > >>>> On Thu, Nov 9, 2017 at 4:32 AM, Tudor Girba <tudor(a)tudorgirba.com> > >>>> wrote: > >>>>> > >>>>> Hi, > >>>>> > >>>>> The basic tools, such as debugger, are expected to work. If something > >>>>> does not work, itâs a bug. > >>>>> > >>>>> Cheers, > >>>>> Doru > >>>>> > >>>>> > >>>>>> On Nov 8, 2017, at 11:59 PM, Tim Mackinnon <tim(a)testit.works> > wrote: > >>>>>> > >>>>>> I think it's broken in Pharo 6 too, as I often find it unreliable. > >>>>>> > >>>>>> It's hard to know what should work anymore - we really need a > >>>>>> stabilisation release to let the dust settle. > >>>>>> > >>>>>> I'm always a bit reticent to report things as I'm not sure what you > >>>>>> expect to work. > >>>>>> > >>>>>> Tim > >>>>>> > >>>>>> Sent from my iPhone > >>>>>> > >>>>>>> On 8 Nov 2017, at 20:40, Stephane Ducasse <stepharo.self(a)gmail.com > > > >>>>>>> wrote: > >>>>>>> > >>>>>>> Hi > >>>>>>> > >>>>>>> I have the following method and I have my cursor -MY CURSOR HERE- > >>>>>>> I select the menu run to here and .... I exit the method. > >>>>>>> :( > >>>>>>> > >>>>>>> Is run to here working in Pharo 70? > >>>>>>> I start to get worry about the number of bugs I get when using > >>>>>>> Pharo70. > >>>>>>> > >>>>>>> Stef > >>>>>>> > >>>>>>> > >>>>>>> fileOut > >>>>>>> "File out the receiver, to a file whose name is a function of the > >>>>>>> change-set name and a unique numeric tag." > >>>>>>> > >>>>>>> | nameToUse | > >>>>>>> self halt. > >>>>>>> self class promptForDefaultChangeSetDirectoryIfNecessary. > >>>>>>> nameToUse := (self defaultChangeSetDirectory / self name , 'cs') > >>>>>>> nextVersion basename. > >>>>>>> UIManager default > >>>>>>> showWaitCursorWhile: > >>>>>>> [ > >>>>>>> | internalStream | > >>>>>>> internalStream := (String new: 10000) writeStream. > >>>>>>> > >>>>>>> -MY CURSOR HERE- > >>>>>>> > >>>>>>> internalStream > >>>>>>> header; > >>>>>>> timeStamp. > >>>>>>> self fileOutPreambleOn: internalStream. > >>>>>>> self fileOutOn: internalStream. > >>>>>>> self fileOutPostscriptOn: internalStream. > >>>>>>> CodeExporter > >>>>>>> writeSourceCodeFrom: internalStream > >>>>>>> baseName: (nameToUse copyFrom: 1 to: nameToUse size - 3) > >>>>>>> isSt: false ] > >>>>>>> > >>>>>> > >>>>> -- > >>>>> www.tudorgirba.com > >>>>> www.feenk.com > >>>>> > >>>>> "Value is always contextual." > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>> > >>> > >> > >> > > > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

Nov. 13, 2017

Re: [Pharo-dev] Pharo6.1 World menu order

by Stephane Ducasse

I would remove also MC from this list. Too many items. :) Stef On Mon, Nov 13, 2017 at 8:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Placing it in the most used tools makes sense to me, because it really is > used a lot. ... so maybe move it just above Monticello Browser :) > > > It breaks muscle memory. > > That's good, because you can finally liberate yourself from the bad memory > and learn cmd+O+B instead. :-D > > Peter > > On Mon, Nov 13, 2017 at 8:37 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: > >> Hi, >> >> I find world menu order in Pharo 6.1. with enable Iceberg a little bit >> awkward :) >> >> [image: Inline images 1] >> >> Any thought on why Iceberg is the first? It breaks muscle memory. >> >> P.S. To fix the order remove `parent: #'MostUsedTools'` >> from IceRepositoriesBrowser class>>#menuCommandOn: so that implementation >> is: >> >> menuCommandOn: aBuilder >> "Add a custom menu item to the world menu" >> <worldMenu> >> >> (aBuilder item: #'Iceberg') >> order: 0.8; >> icon: self icon; >> "parent: #'MostUsedTools'; <-- remove" >> keyText: 'o, i'; >> action: [ self open ]. >> >> >> >> Cheers, >> Alex >> > >

Nov. 13, 2017

Publishing a book with Pillar

by Stephane Ducasse

Hi guys we are working on pillar and we will probably release a new alph version soon. I'm updating the doc. But I found that the doc I was writing can help some of you. Julien is written a nice booklet on USBdrivers and he told me that this doc works super well on mac. Stef

Nov. 13, 2017

Re: [Pharo-dev] Pharo6.1 World menu order

by Peter UhnÃ¡k

Placing it in the most used tools makes sense to me, because it really is used a lot. ... so maybe move it just above Monticello Browser :) > It breaks muscle memory. That's good, because you can finally liberate yourself from the bad memory and learn cmd+O+B instead. :-D Peter On Mon, Nov 13, 2017 at 8:37 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi, > > I find world menu order in Pharo 6.1. with enable Iceberg a little bit > awkward :) > > [image: Inline images 1] > > Any thought on why Iceberg is the first? It breaks muscle memory. > > P.S. To fix the order remove `parent: #'MostUsedTools'` > from IceRepositoriesBrowser class>>#menuCommandOn: so that implementation > is: > > menuCommandOn: aBuilder > "Add a custom menu item to the world menu" > <worldMenu> > > (aBuilder item: #'Iceberg') > order: 0.8; > icon: self icon; > "parent: #'MostUsedTools'; <-- remove" > keyText: 'o, i'; > action: [ self open ]. > > > > Cheers, > Alex >

Nov. 13, 2017