- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo in a read-only environment survey

by Stephane Ducasse

Thanks for the reference. We now have the possibility to create small kernels. So we will start a new phd on improving such an architecture (tooling) and we want to see what we can do. One path is can have miniCog that can co evolve with the kernel and even run way slower. Stef On Mon, Jun 19, 2017 at 5:55 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Jun 15, 2017 at 9:32 PM, JÃ©rÃ©mie Regnault > <jeremie.regnault(a)outlook.com> wrote: >> >> Hi, I'm working on Pharo deployment in a read-only environment, and I >> want to know what behavior you want Pharo to adopt. If you could take >> 5-10 minutes to fill my survey, it would be nice : >> https://goo.gl/forms/8S7w4079NDfBrsVu1 > > > Done. Now I provide my requested suggestion here since theres more room and > more feedback. > > Code at the level of individual methods should be > source-content-addressable, by a hash similar to but not necessarily > identical to git internals > (https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) Then code can > be simultaneously stored to multiple locations - memory and/or separate > writable local file as a cache, plus a remote content-addressable database > and/or POSTing to a simple HTTP server. Code lookup can equally search > multiple locations, update a LRU cache and easily purge it if memory is > constrained, since the identity of the method source remains the *same* in > all cases. > > Further, I envisage an IoT future with Pharo running bare-metal on embedded > microcontrollers** that don't even have a file system, but do have ample > internet bandwidth. When you connect your remote-system-browser to it from > your desktop, the microcontroller doesn't even need to look up the source > code - it just passes the method's source-content-hash to the desktop and > the desktop looks up and displays the source code. Code compilation for the > microcontroller might be done on the desktop and dynamically downloaded and > installed per method in the microcontroller - just bytecode and > source-content-hash! The microcontroller never sees the source, and the > space saving from removing the compiler facilitates smaller targets. > > cheers -ben > > > > **P.S. The latest cool-kid on the block is the Expressif ESP32 > - 240 MHz dual core Tensilica LX6 microcontroller, 600 DMIPS*** > - Integrated 448kB ROM > - Integrated 520 KB SRAM > - Up to 16MB QPSI flash/SRAM > > The Sparkfun ESP32 Thing is available with 4MB flash for US$20. > https://www.sparkfun.com/products/13907 > and are obviously expected to get more powerful and cheaper in the future - > sufficient to directly run Pharo? > > We should cater for such possibilities! Invent the future! > > > *** equivalent to 1997 Mac_G3/266MHz > (https://www.frc.ri.cmu.edu/~hpm/book97/ch3/processor.list.txt) >

June 20, 2017

Re: [Pharo-dev] Found an error

by Ben Coman

Hi Jeremie, I can't see anything definitive in that log. Just a few usual questions... Is this something you can reproduce? (especially in a fresh Image) What packages have you loaded? What OS, VM & Image versions are you using? cheers -ben On Wed, Jun 14, 2017 at 3:53 PM, JÃ©rÃ©mie Regnault < jeremie.regnault(a)outlook.com> wrote: > Hi, > > I just found an error that made my VM crash during a test, I join the > log file for full trace: > > [...] > > TestExecutionEnvironment>>runTestCase: > > Recursive not understood error encountered > > [...] > > SSmalltalk stack dump: > 0xffeed824 M Continuation>initializeFromContext: 0xa272308: a(n) > Continuation > 0xffeed848 I Continuation class>fromContext: 0xa8653d8: a(n) > Continuation class > 0xffeed870 I Continuation class>currentDo: 0xa8653d8: a(n) Continuation > class > 0xffeed894 I ContinuationTest>callcc: 0xd3741a8: a(n) ContinuationTest > 0xffeed8b4 M ContinuationTest>testBlockEscape 0xd3741a8: a(n) > ContinuationTest > 0xffeed8d4 I ContinuationTest(TestCase)>performTest 0xd3741a8: a(n) > ContinuationTest > 0xffeed8ec M [] in ContinuationTest(TestCase)>runCase 0xd3741a8: a(n) > ContinuationTest > 0xffeed90c M BlockClosure>ensure: 0xa272188: a(n) BlockClosure > 0xffeed928 M ContinuationTest(TestCase)>runCase 0xd3741a8: a(n) > ContinuationTest > 0xffeed944 M [] in TestExecutionEnvironment>runTestCaseSafelly: > 0xa26f748: a(n) TestExecutionEnvironment > 0xffeed95c M BlockClosure>on:do: 0xa2720e0: a(n) BlockClosure > 0xffeed980 M [] in TestExecutionEnvironment>runTestCaseSafelly: > 0xa26f748: a(n) TestExecutionEnvironment > 0xffeed998 M BlockClosure>on:do: 0xa271ff8: a(n) BlockClosure > 0xffeed9b8 M TestExecutionEnvironment>runTestCaseSafelly: 0xa26f748: > a(n) TestExecutionEnvironment > 0xffeed9d8 M [] in TestExecutionEnvironment>runTestCase: 0xa26f748: a(n) > TestExecutionEnvironment > 0xffeed9f8 M BlockClosure>ensure: 0xa271f68: a(n) BlockClosure > 0xffeeda18 M [] in TestExecutionEnvironment>runTestCase: 0xa26f748: a(n) > TestExecutionEnvironment > 0xffeeda38 M BlockClosure>ifCurtailed: 0xa271ed8: a(n) BlockClosure > 0xffeeda54 M TestExecutionEnvironment>runTestCase: 0xa26f748: a(n) > TestExecutionEnvironment > 0xffeeda70 M CurrentExecutionEnvironment class>runTestCase: 0xafbb690: > a(n) CurrentExecutionEnvironment class > 0xffeeda8c M ContinuationTest(TestCase)>runCaseManaged 0xd3741a8: a(n) > ContinuationTest > 0xffeedaa8 M [] in TestResult>runCase: 0xd3a0d78: a(n) TestResult > 0xffeedac0 M BlockClosure>on:do: 0xa270298: a(n) BlockClosure > 0xffeedae0 M TestResult>runCase: 0xd3a0d78: a(n) TestResult > 0xffeedafc M ContinuationTest(TestCase)>run: 0xd3741a8: a(n) > ContinuationTest > 0xffeedb1c M [] in TestSuite>runUnmanaged: 0xd3ab018: a(n) TestSuite > 0xffeedb40 M OrderedCollection>do: 0xd3b4420: a(n) OrderedCollection > 0xffeedb60 M [] in TestSuite>runUnmanaged: 0xd3ab018: a(n) TestSuite > 0xffee5914 M BlockClosure>ensure: 0xa270190: a(n) BlockClosure > 0xffee5930 M TestSuite>runUnmanaged: 0xd3ab018: a(n) TestSuite > 0xffee5950 M [] in TestSuite>run: 0xd3ab018: a(n) TestSuite > 0xffee5970 M [] in CurrentExecutionEnvironment class>activate:for: > 0xafbb690: a(n) CurrentExecutionEnvironment class > 0xffee5990 M BlockClosure>ensure: 0xa26f8b8: a(n) BlockClosure > 0xffee59b0 M CurrentExecutionEnvironment class>activate:for: 0xafbb690: > a(n) CurrentExecutionEnvironment class > 0xffee59d0 M > TestExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0xa26f748: a(n) TestExecutionEnvironment > 0xffee59ec M DefaultExecutionEnvironment>runTestsBy: 0xb2fa508: a(n) > DefaultExecutionEnvironment > 0xffee5a08 M CurrentExecutionEnvironment class>runTestsBy: 0xafbb690: > a(n) CurrentExecutionEnvironment class > 0xffee5a24 M TestSuite>run: 0xd3ab018: a(n) TestSuite > 0xffee5a40 M [] in TestRunner>runSuite: 0xd29f930: a(n) TestRunner > 0xffee5a60 M BlockClosure>cull:cull: 0xa26f408: a(n) BlockClosure > 0xffee5a88 M [] in TestRunner>executeSuite:as: 0xd29f930: a(n) TestRunner > 0xffee5aa8 M BlockClosure>ensure: 0xa26f698: a(n) BlockClosure > 0xffee5ac4 M TestRunner>executeSuite:as: 0xd29f930: a(n) TestRunner > 0xffee5ae4 M TestRunner>runSuite: 0xd29f930: a(n) TestRunner > 0xffee5b00 M [] in TestRunner>runTestSuites: 0xd29f930: a(n) TestRunner > 0xffee5b34 M [] in Set(Collection)>do:displayingProgress:every: > 0xd3a5bc8: a(n) Set > 0xffee5b5c M Set>do: 0xd3a5bc8: a(n) Set > 0xd446d60 s [] in Set(Collection)>do:displayingProgress:every: > 0xd45c728 s BlockClosure>cull: > 0xd462fe8 s [] in Job>run > 0xd463480 s [] in CurrentJob(DynamicVariable)>value:during: > 0xd463790 s BlockClosure>ensure: > 0xd447088 s CurrentJob(DynamicVariable)>value:during: > 0xd45c788 s CurrentJob class(DynamicVariable class)>value:during: > 0xd4470e8 s [] in Job>run > 0xd447160 s BlockClosure>ensure: > 0xd446e38 s Job>run > 0xd45c518 s MorphicUIManager(UIManager)>displayProgress:from:to:during: > 0xd462e68 s ByteString(String)>displayProgressFrom:to:during: > 0xd4454f8 s Set(Collection)>do:displayingProgress:every: > 0xd45c578 s Set(Collection)>do:displayingProgress: > 0xd446d00 s [] in TestRunner>runTestSuites: > 0xd45c5d8 s [] in CurrentExecutionEnvironment class>activate:for: > 0xd462ec8 s BlockClosure>ensure: > 0xd446f00 s CurrentExecutionEnvironment class>activate:for: > 0xd45c638 s > TestExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0xd462f28 s DefaultExecutionEnvironment>runTestsBy: > 0xd463420 s CurrentExecutionEnvironment class>runTestsBy: > 0xd446dd8 s TestRunner>runTestSuites: > 0xd45c2a8 s TestRunner>runAll > 0xd462ce8 s PluggableButtonMorph>performAction: > 0xd463300 s [] in PluggableButtonMorph>mouseUp: > 0xd3a5c40 s Array(SequenceableCollection)>do: > 0xd3a5ca0 s PluggableButtonMorph>mouseUp: > 0xd45c388 s PluggableButtonMorph(Morph)>handleMouseUp: > 0xd462d48 s MouseButtonEvent>sentTo: > 0xd463360 s PluggableButtonMorph(Morph)>handleEvent: > 0xd4636d0 s PluggableButtonMorph(Morph)>handleFocusEvent: > 0xd463d60 s [] in HandMorph>sendFocusEvent:to:clear: > 0xd463fe0 s BlockClosure>on:do: > 0xd3a5d78 s WorldMorph(PasteUpMorph)>becomeActiveDuring: > 0xd3a5dd8 s HandMorph>sendFocusEvent:to:clear: > 0xd45c3e8 s HandMorph>sendEvent:focus:clear: > 0xd3a5e50 s HandMorph>sendMouseEvent: > 0xd45c448 s HandMorph>handleEvent: > 0xd462da8 s MouseClickState>handleEvent:from: > 0xd4633c0 s HandMorph>handleEvent: > 0xd463730 s HandMorph>processEventsFromQueue: > 0xd463dc0 s HandMorph>processEvents > 0xd464040 s [] in WorldState>doOneCycleNowFor: > 0xd4640a0 s Array(SequenceableCollection)>do: > 0xd464100 s WorldState>handsDo: > 0xd3a5f28 s WorldState>doOneCycleNowFor: > 0xd45c4a8 s WorldState>doOneCycleFor: > 0xd462e08 s WorldMorph>doOneCycle > 0xd3a5f88 s WorldMorph class>doOneCycle > 0xcfcbeb0 s [] in MorphicUIManager>spawnNewProcess > 0xcfcbf10 s [] in BlockClosure>newProcessmalltalk stack dump: > 0xffeed824 M Continuation>initializeFromContext: 0xa272308: a(n) > Continuation > 0xffeed848 I Continuation class>fromContext: 0xa8653d8: a(n) > Continuation class > 0xffeed870 I Continuation class>currentDo: 0xa8653d8: a(n) Continuation > class > 0xffeed894 I ContinuationTest>callcc: 0xd3741a8: a(n) ContinuationTest > 0xffeed8b4 M ContinuationTest>testBlockEscape 0xd3741a8: a(n) > ContinuationTest > 0xffeed8d4 I ContinuationTest(TestCase)>performTest 0xd3741a8: a(n) > ContinuationTest > 0xffeed8ec M [] in ContinuationTest(TestCase)>runCase 0xd3741a8: a(n) > ContinuationTest > 0xffeed90c M BlockClosure>ensure: 0xa272188: a(n) BlockClosure > 0xffeed928 M ContinuationTest(TestCase)>runCase 0xd3741a8: a(n) > ContinuationTest > 0xffeed944 M [] in TestExecutionEnvironment>runTestCaseSafelly: > 0xa26f748: a(n) TestExecutionEnvironment > 0xffeed95c M BlockClosure>on:do: 0xa2720e0: a(n) BlockClosure > 0xffeed980 M [] in TestExecutionEnvironment>runTestCaseSafelly: > 0xa26f748: a(n) TestExecutionEnvironment > 0xffeed998 M BlockClosure>on:do: 0xa271ff8: a(n) BlockClosure > 0xffeed9b8 M TestExecutionEnvironment>runTestCaseSafelly: 0xa26f748: > a(n) TestExecutionEnvironment > 0xffeed9d8 M [] in TestExecutionEnvironment>runTestCase: 0xa26f748: a(n) > TestExecutionEnvironment > 0xffeed9f8 M BlockClosure>ensure: 0xa271f68: a(n) BlockClosure > 0xffeeda18 M [] in TestExecutionEnvironment>runTestCase: 0xa26f748: a(n) > TestExecutionEnvironment > 0xffeeda38 M BlockClosure>ifCurtailed: 0xa271ed8: a(n) BlockClosure > 0xffeeda54 M TestExecutionEnvironment>runTestCase: 0xa26f748: a(n) > TestExecutionEnvironment > 0xffeeda70 M CurrentExecutionEnvironment class>runTestCase: 0xafbb690: > a(n) CurrentExecutionEnvironment class > 0xffeeda8c M ContinuationTest(TestCase)>runCaseManaged 0xd3741a8: a(n) > ContinuationTest > 0xffeedaa8 M [] in TestResult>runCase: 0xd3a0d78: a(n) TestResult > 0xffeedac0 M BlockClosure>on:do: 0xa270298: a(n) BlockClosure > 0xffeedae0 M TestResult>runCase: 0xd3a0d78: a(n) TestResult > 0xffeedafc M ContinuationTest(TestCase)>run: 0xd3741a8: a(n) > ContinuationTest > 0xffeedb1c M [] in TestSuite>runUnmanaged: 0xd3ab018: a(n) TestSuite > 0xffeedb40 M OrderedCollection>do: 0xd3b4420: a(n) OrderedCollection > 0xffeedb60 M [] in TestSuite>runUnmanaged: 0xd3ab018: a(n) TestSuite > 0xffee5914 M BlockClosure>ensure: 0xa270190: a(n) BlockClosure > 0xffee5930 M TestSuite>runUnmanaged: 0xd3ab018: a(n) TestSuite > 0xffee5950 M [] in TestSuite>run: 0xd3ab018: a(n) TestSuite > 0xffee5970 M [] in CurrentExecutionEnvironment class>activate:for: > 0xafbb690: a(n) CurrentExecutionEnvironment class > 0xffee5990 M BlockClosure>ensure: 0xa26f8b8: a(n) BlockClosure > 0xffee59b0 M CurrentExecutionEnvironment class>activate:for: 0xafbb690: > a(n) CurrentExecutionEnvironment class > 0xffee59d0 M > TestExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0xa26f748: a(n) TestExecutionEnvironment > 0xffee59ec M DefaultExecutionEnvironment>runTestsBy: 0xb2fa508: a(n) > DefaultExecutionEnvironment > 0xffee5a08 M CurrentExecutionEnvironment class>runTestsBy: 0xafbb690: > a(n) CurrentExecutionEnvironment class > 0xffee5a24 M TestSuite>run: 0xd3ab018: a(n) TestSuite > 0xffee5a40 M [] in TestRunner>runSuite: 0xd29f930: a(n) TestRunner > 0xffee5a60 M BlockClosure>cull:cull: 0xa26f408: a(n) BlockClosure > 0xffee5a88 M [] in TestRunner>executeSuite:as: 0xd29f930: a(n) TestRunner > 0xffee5aa8 M BlockClosure>ensure: 0xa26f698: a(n) BlockClosure > 0xffee5ac4 M TestRunner>executeSuite:as: 0xd29f930: a(n) TestRunner > 0xffee5ae4 M TestRunner>runSuite: 0xd29f930: a(n) TestRunner > 0xffee5b00 M [] in TestRunner>runTestSuites: 0xd29f930: a(n) TestRunner > 0xffee5b34 M [] in Set(Collection)>do:displayingProgress:every: > 0xd3a5bc8: a(n) Set > 0xffee5b5c M Set>do: 0xd3a5bc8: a(n) Set > 0xd446d60 s [] in Set(Collection)>do:displayingProgress:every: > 0xd45c728 s BlockClosure>cull: > 0xd462fe8 s [] in Job>run > 0xd463480 s [] in CurrentJob(DynamicVariable)>value:during: > 0xd463790 s BlockClosure>ensure: > 0xd447088 s CurrentJob(DynamicVariable)>value:during: > 0xd45c788 s CurrentJob class(DynamicVariable class)>value:during: > 0xd4470e8 s [] in Job>run > 0xd447160 s BlockClosure>ensure: > 0xd446e38 s Job>run > 0xd45c518 s MorphicUIManager(UIManager)>displayProgress:from:to:during: > 0xd462e68 s ByteString(String)>displayProgressFrom:to:during: > 0xd4454f8 s Set(Collection)>do:displayingProgress:every: > 0xd45c578 s Set(Collection)>do:displayingProgress: > 0xd446d00 s [] in TestRunner>runTestSuites: > 0xd45c5d8 s [] in CurrentExecutionEnvironment class>activate:for: > 0xd462ec8 s BlockClosure>ensure: > 0xd446f00 s CurrentExecutionEnvironment class>activate:for: > 0xd45c638 s > TestExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0xd462f28 s DefaultExecutionEnvironment>runTestsBy: > 0xd463420 s CurrentExecutionEnvironment class>runTestsBy: > 0xd446dd8 s TestRunner>runTestSuites: > 0xd45c2a8 s TestRunner>runAll > 0xd462ce8 s PluggableButtonMorph>performAction: > 0xd463300 s [] in PluggableButtonMorph>mouseUp: > 0xd3a5c40 s Array(SequenceableCollection)>do: > 0xd3a5ca0 s PluggableButtonMorph>mouseUp: > 0xd45c388 s PluggableButtonMorph(Morph)>handleMouseUp: > 0xd462d48 s MouseButtonEvent>sentTo: > 0xd463360 s PluggableButtonMorph(Morph)>handleEvent: > 0xd4636d0 s PluggableButtonMorph(Morph)>handleFocusEvent: > 0xd463d60 s [] in HandMorph>sendFocusEvent:to:clear: > 0xd463fe0 s BlockClosure>on:do: > 0xd3a5d78 s WorldMorph(PasteUpMorph)>becomeActiveDuring: > 0xd3a5dd8 s HandMorph>sendFocusEvent:to:clear: > 0xd45c3e8 s HandMorph>sendEvent:focus:clear: > 0xd3a5e50 s HandMorph>sendMouseEvent: > 0xd45c448 s HandMorph>handleEvent: > 0xd462da8 s MouseClickState>handleEvent:from: > 0xd4633c0 s HandMorph>handleEvent: > 0xd463730 s HandMorph>processEventsFromQueue: > 0xd463dc0 s HandMorph>processEvents > 0xd464040 s [] in WorldState>doOneCycleNowFor: > 0xd4640a0 s Array(SequenceableCollection)>do: > 0xd464100 s WorldState>handsDo: > 0xd3a5f28 s WorldState>doOneCycleNowFor: > 0xd45c4a8 s WorldState>doOneCycleFor: > 0xd462e08 s WorldMorph>doOneCycle > 0xd3a5f88 s WorldMorph class>doOneCycle > 0xcfcbeb0 s [] in MorphicUIManager>spawnNewProcess > 0xcfcbf10 s [] in BlockClosure>newProcess > > > > -- > JÃ©rÃ©mie Regnault > portable : 06.41.93.47.26 >

June 20, 2017

GitHub survey on open source projects

by Eliot Miranda

Not sure how much this reflects our communities but this is interesting. GitHub Survey: Open Source Is Popular, Plagued by Poor Docs and Rude People https://adtmag.com/articles/2017/06/05/open-source-survey.aspx _,,,^..^,,,_

June 19, 2017

Re: [Pharo-dev] Pharo in a read-only environment survey

by Ben Coman

On Thu, Jun 15, 2017 at 9:32 PM, JÃ©rÃ©mie Regnault < jeremie.regnault(a)outlook.com> wrote: > Hi, I'm working on Pharo deployment in a read-only environment, and I > want to know what behavior you want Pharo to adopt. If you could take > 5-10 minutes to fill my survey, it would be nice : > https://goo.gl/forms/8S7w4079NDfBrsVu1 Done. Now I provide my requested suggestion here since theres more room and more feedback. Code at the level of individual methods should be source-content-addressable, by a hash similar to but not necessarily identical to git internals (https://git-scm.com/book/en/ v1/Git-Internals-Git-Objects). Then code can be simultaneously stored to multiple locations - memory and/or separate writable local file as a cache, plus a remote content-addressable database and/or POSTing to a simple HTTP server. Code lookup can equally search multiple locations, update a LRU cache and easily purge it if memory is constrained, since the identity of the method source remains the *same* in all cases. Further, I envisage an IoT future with Pharo running bare-metal on embedded microcontrollers** that don't even have a file system, but do have ample internet bandwidth. When you connect your remote-system-browser to it from your desktop, the microcontroller doesn't even need to look up the source code - it just passes the method's source-content-hash to the desktop and the desktop looks up and displays the source code. Code compilation for the microcontroller might be done on the desktop and dynamically downloaded and installed per method in the microcontroller - just bytecode and source-content-hash! The microcontroller never sees the source, and the space saving from removing the compiler facilitates smaller targets. cheers -ben **P.S. The latest cool-kid on the block is the Expressif ESP32 - 240 MHz dual core Tensilica LX6 microcontroller, 600 DMIPS*** - Integrated 448kB ROM - Integrated 520 KB SRAM - Up to 16MB QPSI flash/SRAM The Sparkfun ESP32 Thing is available with 4MB flash for US$20. https://www.sparkfun.com/products/13907 and are obviously expected to get more powerful and cheaper in the future - sufficient to directly run Pharo? We should cater for such possibilities! Invent the future! *** equivalent to 1997 Mac_G3/266MHz ( https://www.frc.ri.cmu.edu/~hpm/book97/ch3/processor.list.txt)

June 19, 2017

Re: [Pharo-dev] aSortedCollection collect: returns OrderedCollection instead of original sorted

by phil＠highoctane.be

+100 On Mon, Jun 19, 2017 at 2:14 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > You can do anything in the collect block, so the returned objects possibly > cannot be sorted, and even if it can be sorted maybe the sort block is not > compatible. > > On Mon, Jun 19, 2017 at 6:04 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Hi. >> >> I just found that >> >> >> #() asSortedCollection select: [ ] => SortedCollection >> #() asSortedCollection collect: [ ] => OrderedCollection >> >> >> It feels like a bug to me. But maybe there is a reason why sorted >> collection collects items as OrderedCollection instead of original kind of >> sort? >> >> My usercase was copy of object with sorted collection inside. For this I >> just manually collect copy of each item. But at the end my copy became >> broken because of sort was important for domain logic. >> >> Best regards, >> Denis >> > >

June 19, 2017

Re: [Pharo-dev] aSortedCollection collect: returns OrderedCollection instead of original sorted

by Gabriel Cotelli

You can do anything in the collect block, so the returned objects possibly cannot be sorted, and even if it can be sorted maybe the sort block is not compatible. On Mon, Jun 19, 2017 at 6:04 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > I just found that > > > #() asSortedCollection select: [ ] => SortedCollection > #() asSortedCollection collect: [ ] => OrderedCollection > > > It feels like a bug to me. But maybe there is a reason why sorted > collection collects items as OrderedCollection instead of original kind of > sort? > > My usercase was copy of object with sorted collection inside. For this I > just manually collect copy of each item. But at the end my copy became > broken because of sort was important for domain logic. > > Best regards, > Denis >

June 19, 2017

Re: [Pharo-dev] Esteban's ChangeLog week of 12 June 2017

by Serge Stinckwich

On Mon, Jun 19, 2017 at 12:40 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> On 19 Jun 2017, at 13:22, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> On Mon, Jun 19, 2017 at 7:00 AM, <estebanlm(a)gmail.com> wrote: >>> Hello! >>> >>> This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017. >>> You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=12/6/2017&to=18/6/2017 >>> >>> ChangeLog >>> ========= >>> >>> 15 June 2017: >>> ------------- >>> >>> * I finished an iteration for allowing cherry-pick into [iceberg](http://github.com/pharo-vcs/iceberg). >>> >>> Now, I just need to make it work on 64bits and we will be ready-to-go for releasing it :) >> >> Great work Esteban ! >> >> Cherry-picking is integrated with Kommiter or the UI is completely different ? > > is a different implementation. Is integrated into iceberg (you will see the checkboxes when commiting). > Kommiter in fact does not works since ages. Yes it was working more or less and I like it ! If we have a similar interface in Iceberg, this will be great :-) -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 19, 2017

Re: [Pharo-dev] Esteban's ChangeLog week of 12 June 2017

by Esteban Lorenzano

> On 19 Jun 2017, at 13:22, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > On Mon, Jun 19, 2017 at 7:00 AM, <estebanlm(a)gmail.com> wrote: >> Hello! >> >> This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017. >> You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=12/6/2017&to=18/6/2017 >> >> ChangeLog >> ========= >> >> 15 June 2017: >> ------------- >> >> * I finished an iteration for allowing cherry-pick into [iceberg](http://github.com/pharo-vcs/iceberg). >> >> Now, I just need to make it work on 64bits and we will be ready-to-go for releasing it :) > > Great work Esteban ! > > Cherry-picking is integrated with Kommiter or the UI is completely different ? is a different implementation. Is integrated into iceberg (you will see the checkboxes when commiting). Kommiter in fact does not works since ages. Esteban > > Regards, > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/

June 19, 2017

Re: [Pharo-dev] Esteban's ChangeLog week of 12 June 2017

by Serge Stinckwich

On Mon, Jun 19, 2017 at 7:00 AM, <estebanlm(a)gmail.com> wrote: > Hello! > > This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=12/6/2017&to=18/6/2017 > > ChangeLog > ========= > > 15 June 2017: > ------------- > > * I finished an iteration for allowing cherry-pick into [iceberg](http://github.com/pharo-vcs/iceberg). > > Now, I just need to make it work on 64bits and we will be ready-to-go for releasing it :) Great work Esteban ! Cherry-picking is integrated with Kommiter or the UI is completely different ? Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 19, 2017

Re: [Pharo-dev] debug vm windows?

by Peter Uhnak

Hi, the instructions are not merged yet and I am not sure whether something has changed since I wrote it (April 8), but I wrote down instructions and created scripts for building the VM on Windows (7+) https://github.com/pharo-project/pharo-vm/pull/128 https://github.com/peteruhnak/pharo-vm/blob/windows-build/README-Win32.md https://github.com/peteruhnak/pharo-vm/tree/windows-build/scripts/windows in particular the Manual Compilation at the end; iirc `mvm -a` creates asserting VM, `mvm -d` debug, `mvm -f` regular, and `mvm -A` all of them. Peter On Tue, Jun 13, 2017 at 10:57:45PM +0200, phil(a)highoctane.be wrote: > Not at the moment. > > On Tue, Jun 13, 2017 at 10:08 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > > > Thanks! Any chance you can redo the build to get also a debug vm for > > the latest version? > > > > Cheers, > > Andrei > > > > On Tue, Jun 13, 2017 at 8:02 PM, phil(a)highoctane.be <phil(a)highoctane.be> > > wrote: > > > I have an older build here. > > > > > > https://ci.appveyor.com/project/philippeback/pharo-vm > > > > > > https://bintray.com/pharophile/pharo-vm/build/ > > view/files?sort=name&order=asc#files/ > > > > > > There is an normal, assert and debug vm in there. > > > > > > Phil > > > > > > On Tue, Jun 13, 2017 at 7:14 PM, Andrei Chis <chisvasileandrei(a)gmail.com > > > > > > wrote: > > >> > > >> Hi, > > >> > > >> Is there a Pharo debug vm for windows already build and available > > >> somewhere? > > >> > > >> Cheers, > > >> Andrei > > >> > > > > > > >

June 19, 2017