May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] RewriteTool

by Sean P. DeNigris

Sean P. DeNigris wrote > ...update the migration BTW why "firstVersion: spec <version: 'firstVersion'>". I've never seen this approach before. What is the reason to depart from numbered versions? ----- Cheers, Sean -- View this message in context: http://forum.world.st/RewriteTool-tp4824877p4825102.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 7, 2015

Re: [Pharo-dev] RewriteTool

by Sean P. DeNigris

Mark Rizun wrote > I will update the PharoExtras/RewriteTool repo soon. I noticed your personal repo was available for a moment, and took the opportunity to update the migration ----- Cheers, Sean -- View this message in context: http://forum.world.st/RewriteTool-tp4824877p4825101.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 7, 2015

Re: [Pharo-dev] [Ann] The Garage database driver API

by Esteban A. Maringolo

Regarding the GlorpDBX in metarepo, I uploaded a few packages and configs last week to Glorp & GlorpDBX, does the metarepo get updated automatically? Esteban A. Maringolo 2015-05-07 9:35 GMT-03:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Yes, I could :P. Can you open an issue so I do not forget? > > https://github.com/guillep/DBXTalk > > :) > > El jue., 7 de may. de 2015 a la(s) 2:30 p. m., Sean P. DeNigris > <sean(a)clipperadams.com> escribiÃ³: >> >> Cool!! >> >> >> Guillermo Polito wrote >> > [2] http://guillep.github.io/DBXTalk/garage/ >> >> Nitpick - could you change "Pharo language" to "Pharo environment" or just >> Pharo with a link? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Ann-The-Garage-database-driver-API-tp4825006p4825032.… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >

May 7, 2015

Re: [Pharo-dev] Debugger hangs vm on step into

by Ben Coman

On Thu, May 7, 2015 at 9:09 PM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Le 05/05/2015 14:35, Ben Coman a Ã©crit : > >> Not sure if this is related, but if you put a haltOnce at the top of >> SpecDebugger>>updateReceiverInspectorFromContext: >> then step down until the 'receiver' temporary variable is set, >> then inspect 'receiver', the system hangs. >> cheers -ben >> >> >> After digging into it, the cause of the hang is now obvious, but the > simplest solution makes me perplex > and does not cover other cases (ProcessLocalVariables, see below). > > The problem comes from the display of the object in the lower pane of the > debugger > that locks itself because the monitor is owned by the debugged process. > (the inspector ends up in a call to xxx>>printOn: aStream to display the > object > and SharedQueue>>printOn: aStream starts with a critical block on the > monitor). > So we could be hanged in various ways : clicking on the debugger stack on > the Sharedqueue context, > opening an inspector on the Sharedqueue etc). > A simple solution is to evaluate the printOn: in the context of the owner > process > in SharedQueue (tested and works), but it is specific to SharedQueue. > > Does the #printOn: really need a monitor? What is it protecting? * not the stream, that is passed in as a parameter from a single thread * not the class name, that is handled normally * items size does "^ lastIndex - firstIndex + 1" in OrderedCollection, which presumably will be inlined and not interruptible, and even if it could be interrupted part way through the calculation to become inconsistent, the value is only printed, so do we really care? For reference... SharedQueue>>printOn: aStream monitor critical: [ aStream nextPutAll: self class name; nextPutAll: ' with '; print: items size; nextPutAll: ' items' ]. > When an inspector ask an object to print itself, it does not take into > account the "effective/owner process " part of the object. > > For example for ProcessLocalVariable (and descendants) it does not work: > | process variable | > process := [ variable := ProcessLocalVariable value: 'hello world' ] > forkAt: Processor userInterruptPriority . variable value => evaluates to nil > > this makes it difficult (impossible ?) to inspect/debug - a workaround > would be to track the effective process near the host in the inspector (in > AbstractEyeElement?) but it could be tricky and I do not know implications > here. > > I am not clear on the semantics we want debugging ProcessLocalVariable, however if without forking I do... variable := ProcessLocalVariable value: 'hello world' then inspecting /variable/ shows me only... self: a ProcessLocalVariable index: 6 And there is no change when forking... process := [ variable := ProcessLocalVariable value: 'hello world'. variable inspect. ] fork. Also, the following works as expected with respect to the /result/ variable. | process variable result | process := [ variable := ProcessLocalVariable value: 'hello world'. self halt. result := variable value. ] fork. So as ProcessLocalVariable is currently displayed in the debugger there seems no problem (?) for what the debugger displays. cheers -ben | process variable result | process := [ variable := ProcessLocalVariable value: 'hello world'. self halt. result := variable value. ] fork.

May 7, 2015

Re: [Pharo-dev] Selected context specific debugger action

by Yuriy Tymchuk

Next to buttons. I want to make an indicator for a selected method. Buy the way, can you direct me at where should I start to look in GTDebugger. Because Iâm quite new with it. Uko > On 07 May 2015, at 16:58, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Where do you want these actions to be placed? > In the menu of the stack or next to the stepInto/Over etc buttons? > > Cheers, > Andrei > > On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > Hi, > > is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context? > > Uko >

May 7, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50039 Home: https://github.com/pharo-project/pharo-core

May 7, 2015

[pharo-project/pharo-core] f22176: 50039

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: f22176c65834be28372208e6add9f57a39f1b644 https://github.com/pharo-project/pharo-core/commit/f22176c65834be28372208e6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-07 (Thu, 07 May 2015) Changed paths: M Kernel.package/Character.class/instance/printing/hex.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script647.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script648.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50038.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50039.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/extension/Behavior/instance/layout.st Log Message: ----------- 50039 15286 `Class new` doesnt result in a properly initialized class object. https://pharo.fogbugz.com/f/cases/15286 15506 Hexadecimal is misspelled in Character>>#hex https://pharo.fogbugz.com/f/cases/15506 http://files.pharo.org/image/50/50039.zip

May 7, 2015

[Review]: Issue 15507: SliceMaker Overhaul

by Sean P. DeNigris

Issue 15507: SliceMaker Overhaul https://pharo.fogbugz.com/default.asp?15507 It all started simply enough: I wanted to extract the issue title downloading - which is generally useful - from slice maker. One full day later, I ended up with a pretty extensive rewrite. Now, I feel like it would've been better to start from scratch, but IMHO it's better, and good enough to move on to more pressing things. Fix in inbox: SLICE-Issue-15507-SliceMaker-Overhaul-SeanDeNigris.1 ###[FEATURE]: PharoIssue class. Here is it's class comment: I represent a Pharo development issue. Responsibilities: - create text templates (e.g. for the mailing list or issue tracker comments) for common events like issue creation and slice submission - communicate with the issue tracker Collaborators: - ZnClient - my link to the issue tracker - MCSliceInfo - I can get you one if you need it Public API and Key Messages: Most of my behavior is illustrated in my tests. The noticable exception are my text template creation messages, the testing of which seemed to hurt as much in duplication as it added in QA. ###[Cleanup]: Komitter - Remove Duplication Caused By MCSliceInfo - For some reason, Komitter seems to deal with MCPackages, while MCSliceInfo deals with MCWorkingCopy instances. This causes a tiny difference when making a slice (one sends #package to the wc, the other already has the package). The previous solution was to copy/paste a long method, changing one statement. This one trades that method in for "MCPackage>>#package ^ self" with a careful explanation in the comment of why we are doing this ugly thing! ###[ENH]: MC Slice Making - This is the most significant change - Extract issue-related behavior to PharoIssue - Extract slice-related behavior to MCSliceInfo. This class is still pretty confusing. It's a cross between a model of an actual slice, and an Application Model for MCSliceMaker. But since slices are supposed to go away soon... - Many small cleanups - fix misspellings, improve comments, simplify code - Remove the "Grab" button. The issue title is automatically downloaded when the issue number field loses focus ----- Cheers, Sean -- View this message in context: http://forum.world.st/Review-Issue-15507-SliceMaker-Overhaul-tp4825070.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 7, 2015

Re: [Pharo-dev] [Ann] The Garage database driver API

by Sean P. DeNigris

Guillermo Polito wrote > Can you open an issue so I do not forget? https://github.com/guillep/DBXTalk/issues/6 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ann-The-Garage-database-driver-API-tp4825006p4825069.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 7, 2015

Re: [Pharo-dev] Selected context specific debugger action

by Eliot Miranda

Hi Tudor, could you describe the client-side API and give some examples? I'm in squeak most if the time so GT is not easily accessible but perhaps the facility could be back ported. I'd love to have this facility for making the CM simulator easier to step through. Eliot (phone) On May 7, 2015, at 7:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > You should be able to do that in the GTDebugger (it was made exactly for that). > > Doru > > On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Hi, >> >> is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context? >> >> Uko > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

May 7, 2015