- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Bulk] via Arden Thomas, the annual stackoverflow programming language survey is open. Let's try and get visibility for Smalltalk

by Yanni Chiu

Done. It took practically the whole 10 minutes they said it would - mainly because of all the ârecruiterâ questions they asked. Hereâs my answer to the free-form questions at the end: 44. If we could add one thing to Stack Overflow just for you, what would it be? More Smalltalk-friendly. I'm not a significant user because Smalltalk is poorly covered. From what I've heard, it's because a mob that is ignorant of Smalltalk keeps censoring anything to do with Smalltalk. 45. What excites you about being a programmer in 2016 and beyond? We're just getting started. Only a generational change will rid us of the static-type mindset. On Jan 25, 2016, at 12:24 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > http://meta.stackoverflow.com/questions/314186/stack-overflow-annual-survey… > > > Should take less than 10 minutes to fill out. You might want to send this on to programming teams working in companies using Smalltalk. > > _,,,^..^,,,_ > best, Eliot

Jan. 25, 2016

via Arden Thomas, the annual stackoverflow programming language survey is open. Let's try and get visibility for Smalltalk

by Eliot Miranda

http://meta.stackoverflow.com/questions/314186/stack-overflow-annual-survey… Should take less than 10 minutes to fill out. You might want to send this on to programming teams working in companies using Smalltalk. _,,,^..^,,,_ best, Eliot

Jan. 25, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 25, 2016

[pharo-project/pharo-core] 235383: 50547

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 2353838f1184b9334e1ea6be8a98e7cbd492d952 https://github.com/pharo-project/pharo-core/commit/2353838f1184b9334e1ea6be… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-25 (Mon, 25 Jan 2016) Changed paths: R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/README.md R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/accessing/project.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/development support/DevelopmentSupport.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/development support/validate.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/loading/load.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/loading/loadBleedingEdge.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/loading/loadDevelopment.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/metacello tool support/isMetacelloConfig.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/private/baseConfigurationClassIfAbsent_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/private/ensureMetacello.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/class/private/ensureMetacelloBaseConfiguration.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/definition.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/accessing/customProjectAttributes.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/accessing/project.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/baselines/baseline0%5F9_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/external projects/alien_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/external projects/ffi_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/symbolic versions/development_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/symbolic versions/stable_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/versions/v0%5F9%5F0_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/versions/v0%5F9%5F1_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/versions/v0%5F9%5F2_.st R ConfigurationOfFFINB.package/ConfigurationOfFFINB.class/instance/versions/version093_.st M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/stable_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F11%5F1_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F11_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50546.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50547.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50546.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50547.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A UnifiedFFI-Tests.package/FFICalloutMethodBuilderTest.class/instance/tests/testCallWithPointerPointer.st M UnifiedFFI-Tests.package/FFICalloutObjectForTest.class/class/primitives/primCreate_.st M UnifiedFFI-Tests.package/FFICalloutObjectForTest.class/class/primitives/primObject_strcpy_.st R UnifiedFFI-Tests.package/FFICalloutObjectForTest.class/instance/as yet unclassified/method1.st M UnifiedFFI-Tests.package/FFICalloutObjectForTest.class/instance/primitives/primFree.st M UnifiedFFI-Tests.package/FFICalloutObjectForTest.class/instance/primitives/primStrcpy_.st M UnifiedFFI.package/FFICallbackType.class/instance/emitting code/emitArgument_context_.st A UnifiedFFI.package/FFICallbackType.class/instance/emitting code/emitReturnArgument_context_.st M UnifiedFFI.package/FFICalloutMethodBuilder.class/instance/private/generateFFICallout_spec_.st A UnifiedFFI.package/FFIConst.class/instance/emitting code/emitReturnArgument_context_.st M UnifiedFFI.package/FFIExternalArray.class/instance/converting/gcpointer.st A UnifiedFFI.package/FFIExternalArray.class/instance/converting/pointerAutoRelease.st A UnifiedFFI.package/FFIExternalObject.class/class/as yet unclassified/finalizeResourceData_.st A UnifiedFFI.package/FFIExternalObject.class/instance/external resource management/autoRelease.st M UnifiedFFI.package/FFIExternalObject.class/instance/external resource management/registerAsExternalResource.st M UnifiedFFI.package/FFIExternalObject.class/instance/initialization/initialize.st M UnifiedFFI.package/FFIExternalObjectType.class/instance/emitting code/emitArgument_context_.st A UnifiedFFI.package/FFIExternalObjectType.class/instance/emitting code/emitReturnArgument_context_.st A UnifiedFFI.package/FFIExternalResourceManager.class/class/resource management/addResource_executor_.st A UnifiedFFI.package/FFIExternalResourceManager.class/instance/external resource management/addResource_executor_.st M UnifiedFFI.package/FFIExternalType.class/instance/emitting code/emitArgument_context_.st A UnifiedFFI.package/FFIExternalType.class/instance/emitting code/emitReturnArgument_context_.st R UnifiedFFI.package/FFIFunctionArgument.class/instance/emitting code/emitArgument_context_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/emitting code/emitArgument_type_context_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/emitting code/emitArgument_type_context_objectClass_instVarName_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/emitting code/emitPointerArityUnroll_type_context_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/emitting code/emitPointerArityUnroll_type_context_objectClass_instVarName_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private emitting code/addUnroll_fromArity_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private emitting code/emitArgument_context_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private emitting code/emitArgument_context_objectClass_instVarName_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private emitting code/emitPointerArityRoll_context_arity_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private emitting code/emitPointerArityUnroll_context_arity_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private emitting code/emitPointerArityUnroll_context_objectClass_instVarName_arity_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private/needsArityRolling_.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private/rolledPointerTempName.st A UnifiedFFI.package/FFIFunctionArgument.class/instance/private/rolledPointerTempNameFor_.st M UnifiedFFI.package/FFIInstVarArgument.class/instance/emitting code/emitArgument_context_.st R UnifiedFFI.package/FFIInstVarArgument.class/instance/emitting code/emitArgument_context_objectClass_.st A UnifiedFFI.package/FFIInstVarArgument.class/instance/private/rolledPointerTempName.st R UnifiedFFI.package/FFIMethodArgument.class/instance/emitting code/emitArgument_context_.st R UnifiedFFI.package/FFIMethodArgument.class/instance/emitting code/emitArgument_context_objectClass_.st R UnifiedFFI.package/FFIMethodArgument.class/instance/emitting code/emitArgument_context_objectClass_instVarName_.st A UnifiedFFI.package/FFIMethodArgument.class/instance/private emitting code/emitArgument_context_.st A UnifiedFFI.package/FFIMethodArgument.class/instance/private emitting code/emitArgument_context_objectClass_instVarName_.st A UnifiedFFI.package/FFIMethodArgument.class/instance/private/rolledPointerTempName.st R UnifiedFFI.package/FFISelfArgument.class/instance/emitting code/emitArgument_context_objectClass_.st A UnifiedFFI.package/FFISelfArgument.class/instance/emitting code/emitArgument_context_objectClass_instVarName_.st A UnifiedFFI.package/FFISelfArgument.class/instance/private/rolledPointerTempName.st A UnifiedFFI.package/extension/ExternalAddress/instance/adoptAddress_.st A UnifiedFFI.package/extension/ExternalAddress/instance/autoRelease.st A UnifiedFFI.package/extension/ExternalAddress/instance/copyFrom_to_.st M UnifiedFFI.package/extension/ExternalAddress/instance/gcpointer.st A UnifiedFFI.package/extension/ExternalAddress/instance/pointerAutoRelease.st A UnifiedFFI.package/extension/ExternalAddress/instance/registerAsExternalResource.st A UnifiedFFI.package/extension/ExternalAddress/instance/rollToArity_.st A UnifiedFFI.package/extension/ExternalAddress/instance/unrollFromArity_.st A UnifiedFFI.package/extension/ExternalData/instance/copyFrom_to_.st A UnifiedFFI.package/extension/ExternalObject/instance/autoRelease.st A UnifiedFFI.package/extension/ExternalObject/instance/registerAsExternalResource.st Log Message: ----------- 50547 17448 ffi declaration does not understand pointer-pointer https://pharo.fogbugz.com/f/cases/17448 http://files.pharo.org/image/50/50547.zip

Jan. 25, 2016

Re: [Pharo-dev] The shortcuts learnability is awesome, thank you!

by Mariano Martinez Peck

Grab very last image (as of today), evaluate this code: ShortcutReminder enabled: true. (or enable that via settings) And then simply start using the image, and you will see Growl-like popups on the bottom left reminding you the shortcut for the action you just did :) On Mon, Jan 25, 2016 at 11:52 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Any more info about this, I was sick lately and I did not understand what > was that about . > > On Mon, Jan 25, 2016 at 2:45 PM Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> This is just to say a big thanks to all those that contributed to the new >> shortcut learnability. This is awesome. I love it. >> >> Bye, >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > -- Mariano http://marianopeck.wordpress.com

Jan. 25, 2016

Re: [Pharo-dev] The shortcuts learnability is awesome, thank you!

by Dimitris Chloupis

Any more info about this, I was sick lately and I did not understand what was that about . On Mon, Jan 25, 2016 at 2:45 PM Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > This is just to say a big thanks to all those that contributed to the new > shortcut learnability. This is awesome. I love it. > > Bye, > > > -- > Mariano > http://marianopeck.wordpress.com >

Jan. 25, 2016

Re: [Pharo-dev] [Moose-dev] Spur Garbage collection takes 4 times more when loading MSE (WAS: mse loading looks slower :()

by Tudor Girba

Hi Eliot, Indeed, this was a Spur image. I will put together the same setup with a pre-Spur image and get back to you. Cheers, Doru > On Jan 24, 2016, at 11:35 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Doru, > > On Sun, Jan 24, 2016 at 12:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Eliot, > > I created a package to easily reproduce the problem: > https://dl.dropboxusercontent.com/u/18323746/Tmp/moose-6-for-GC-bug.zip > > In there you will get: > - an image, > - the MSE file to be loaded, and > - a Playground script that loads that file. > > I take it that this is a Spur image. t would be great to have both a Spur and a V3 mage to compare, as similar as is easily achievable. But as long as there's both a V3 and a Spur image... > > > On my Mac, this takes some 3 minutes, while before it took about 1 minute. > > Let me know if you need anything else. > > Cheers, > Doru > > > > > On Jan 24, 2016, at 9:33 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi Doru, > > > > On Sun, Jan 24, 2016 at 12:26 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi Eliot, > > > > Thanks for looking at this. > > > > Please let us know what support you need, or what kind of experiments we can do on our side. > > > > What I want most of all is a test case that I can run on Mac. I'm assuming that I can just copy the job that Vincent mentioned in his email and use that as a test case. Do you see any issues with that? If so, how do I get a really bug MOOSE test case to run on Mac? > > > > > > Cheers, > > Doru > > > > > > > On Jan 24, 2016, at 9:20 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > > > Hi Vincent, > > > > > > I'll take a look early this week. There's clearly a bug; the Spur > > > GC is /not/ collecting those dictionaries :-( (thanks Stephan!). > > > Assuming the bug is fixed times should come down (see below). It may > > > be that the bug in Slang that I introduced in December has broken > > > things because I don't see these symptoms in my daily work (but I use > > > the most up-to-date VM version possible ;-) ). But I'm not in denial > > > and look forward to using MOOSE as a good stress case. > > > > > > I do want to say that the GC is not complete. Right now we have a > > > scavenger that works well, and a global GC that has a slow compaction > > > algorithm, and hence there are significant pauses. For example here's > > > what I see as typical in using SPur for VMMaker work: > > > > > > memory 160,432,128 bytes > > > old 153,658,624 bytes (95.8%) > > > young 4,838,224 bytes (3%) > > > used 127,009,928 bytes (79.2%) > > > free 28,126,456 bytes (17.5%) > > > GCs 7,265 (?? ms between GCs) > > > full 36 totalling 13,229 ms (0% uptime), avg 367.5 ms > > > incr 7,229 totalling 6,546 ms (0% uptime), avg 0.9 ms > > > tenures 3,589,063 (avg 0 GCs/tenure) > > > > > > (There's no uptime in the above stats because we're still > > > transitioning Squeak to the 64-bit clock and there are consequently > > > bugs in computing uptime). > > > > > > The plan is to add an incremental global GC so this work is broken up > > > into much smaller pieces. I don't want to see 700ms pauses in global > > > GC; one can't do game animation with that. So an incremental > > > mark-sweep is needed. There are two nice papers we're considering, > > > one from Lua and one for a truly concurrent collector. But time is > > > pressing, so if anyone out there knows GC and is interested in helping > > > this is a nicely self-contained project for which we'd love to have > > > volunteers. > > > > > > _,,,^..^,,,_ (phone) > > > > > >> On Jan 24, 2016, at 3:43 AM, Vincent BLONDEAU <vincent.blondeau(a)polytech-lille.net> wrote: > > >> > > >> Hi, > > >> > > >> I made the benchmarks with the files you provided. I have more or less the > > >> same magnitude: > > >> Version 504: 0:00:01:09.021 > > >> Version 1175: 0:00:02:37.507 > > >> > > >> However, by launching it in the time profiler (MooseModel new > > >> importFromMSEStream: (StandardFileStream readOnlyFileNamed: > > >> 'd:/ArgoUML-0-34.mse')), it takes > > >> 504: 1 min 55 > > >> 1175: 4 min 25 > > >> Well there is a delta... > > >> > > >> After investigation, the standard process has almost the same duration (120 > > >> secs for prespur and 140 secs for spur). > > >> But, there is a large difference in GC time: > > >> > > >> 504: not spur > > >> **Memory** > > >> old +144,822,000 bytes > > >> young -8,293,660 bytes > > >> used +136,528,340 bytes > > >> free -104,186,788 bytes > > >> > > >> **GCs** > > >> full 1 totalling 965ms (1.0% uptime), avg 965.0ms > > >> incr 3264 totalling 42,279ms (33.0% uptime), avg 13.0ms > > >> tenures 2,497 (avg 1 GCs/tenure) > > >> root table 0 overflows > > >> > > >> 1175: spur > > >> **Memory** > > >> old +0 bytes > > >> young +340,048 bytes > > >> used +340,048 bytes > > >> free -340,048 bytes > > >> **GCs** > > >> full 7 totalling 145,003ms (66.0% uptime), avg > > >> 20715.0ms > > >> incr 3288 totalling 30,912ms (14.0% uptime), avg 9.0ms > > >> tenures 7,146,505 (avg 0 GCs/tenure) > > >> root table 0 overflows > > >> > > >> Total GC time > > >> 504: 43 secs > > >> 1175: 176 secs > > >> > > >> See the performance reports attached. > > >> > > >> I let VM people take care of the issue ;) > > >> > > >> Cheers, > > >> Vincent > > >> > > >> -----Original Message----- > > >> From: moose-dev-bounces(a)list.inf.unibe.ch > > >> [mailto:moose-dev-bounces@list.inf.unibe.ch] On Behalf Of Tudor Girba > > >> Sent: dimanche 24 janvier 2016 09:08 > > >> To: Moose-related development > > >> Subject: [Moose-dev] Re: mse loading looks slower :( > > >> > > >> Hi, > > >> > > >> I am talking about the difference between Moose 6 images: > > >> - October 7: > > >> https://ci.inria.fr/moose/job/moose-6.0/504/artifact/moose-6.0.zip > > >> > > >> - yesterday: > > >> https://ci.inria.fr/moose/job/moose-6.0/1175/artifact/moose-6.0.zip > > >> > > >> Multiple things did change, but not in Moose. In the end, I would like to > > >> understand where the slowness comes. Maybe it comes from Spur itself, but > > >> maybe it comes from somewhere else. > > >> > > >> Cheers, > > >> Doru > > >> > > >> > > >> > > >>>> On Jan 24, 2016, at 1:41 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> > > >>> wrote: > > >>> > > >>> Doru...just to be sure it is not a Pharo (image change), when you said > > >> before and after Spur, do you mean a Pharo 5.0 exactly (just before Spur) > > >> and a Pharo JUST after it? Otherwise, the slowness may come from the > > >> difference between the 2 Pharos you are running. > > >>> > > >>> Cheers, > > >>> > > >>> On Sat, Jan 23, 2016 at 5:55 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > >>> Hi, > > >>> > > >>> I am doing some performance testing of Moose with the Spur VM on Mac. > > >>> > > >>> I tried to load an MSE file with ArgoUML 0.34 and on my machine it loads > > >> twice as slow with Spur than before: > > >>> - PreSpur: 0:00:01:07.272 > > >>> - Spur: 0:00:02:10.508 > > >>> > > >>> Here is the reference file: > > >>> https://dl.dropboxusercontent.com/u/18323746/Tmp/ArgoUML-0-34.mse.zip > > >>> > > >>> And here is the script: > > >>> [ > > >>> MooseModel new > > >>> importFromMSEStream: (StandardFileStream > > >> readOnlyFileNamed: > > >>> (FileSystem workingDirectory / 'src' / > > >> 'ArgoUML-0-34' / 'ArgoUML-0-34.mse') fullName). > > >>> ] timeToRun > > >>> > > >>> Do you get the same? > > >>> > > >>> Cheers, > > >>> Doru > > >>> > > >>> > > >>> -- > > >>> www.tudorgirba.com > > >>> www.feenk.com > > >>> > > >>> "Problem solving should be focused on describing the problem in a way > > >>> that makes the solution obvious." > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> _______________________________________________ > > >>> Moose-dev mailing list > > >>> Moose-dev(a)list.inf.unibe.ch > > >>> https://www.list.inf.unibe.ch/listinfo/moose-dev > > >>> > > >>> > > >>> > > >>> -- > > >>> Mariano > > >>> http://marianopeck.wordpress.com > > >>> _______________________________________________ > > >>> Moose-dev mailing list > > >>> Moose-dev(a)list.inf.unibe.ch > > >>> https://www.list.inf.unibe.ch/listinfo/moose-dev > > >> > > >> -- > > >> www.tudorgirba.com > > >> www.feenk.com > > >> > > >> "What is more important: To be happy, or to make happy?" > > >> > > >> _______________________________________________ > > >> Moose-dev mailing list > > >> Moose-dev(a)list.inf.unibe.ch > > >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > >> <report504.txt> > > >> <report1175.txt> > > > > > > > > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > > -- > _,,,^..^,,,_ > best, Eliot > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Jan. 25, 2016

Remove or disable GTExampleOrganizer

by Nicolai Hess

17471 <https://pharo.fogbugz.com/f/cases/17471/Remove-or-disable-GTExampleOrganizer> Remove or disable GTExampleOrganizer

Jan. 25, 2016

Re: [Pharo-dev] Why the Spotter list is truncated?

by Blondeau Vincent

https://pharo.fogbugz.com/f/cases/17469/Spotter-list-is-truncated Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Tudor Girba > EnvoyÃ© : lundi 25 janvier 2016 14:43 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] Why the Spotter list is truncated? > > Hi, > > This is indeed a bug that we noticed. It is not yet in Pharo, but it will be soon. > It is due to the new infrastructure to allow expanding a category in place > when it is the only one available. > > In the meantime, you can use: "printOn: #sendersâ and it will work for now. > > Please open a bug report in the Pharo bug tracker. > > Cheers, > Doru > > > > > On Jan 25, 2016, at 2:16 PM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > > Hi, > > > > On a Moose image (should have the problem on a Pharo image too), I > wanted to inspect the senders of printOn: (~ 400 results). > > The end of the list finishes at MBVersionInfo>>printOn:â¦ Where are the > others??? : > > <image001.png> > > > > Moreover, on the first page, I have to go in the sender sublist to be able to > click on the arrow to have the listâ¦ and clicking on #senders does nothingâ¦. > > > > <image002.png> > > > > Thanks in advance for solving the issues, > > > > Cheers > > Vincent > > > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout virus, > l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne > saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 25, 2016

Re: [Pharo-dev] Why the Spotter list is truncated?

by Tudor Girba

Hi, This is indeed a bug that we noticed. It is not yet in Pharo, but it will be soon. It is due to the new infrastructure to allow expanding a category in place when it is the only one available. In the meantime, you can use: "printOn: #sendersâ and it will work for now. Please open a bug report in the Pharo bug tracker. Cheers, Doru > On Jan 25, 2016, at 2:16 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > On a Moose image (should have the problem on a Pharo image too), I wanted to inspect the senders of printOn: (~ 400 results). > The end of the list finishes at MBVersionInfo>>printOn:â¦ Where are the others??? : > <image001.png> > > Moreover, on the first page, I have to go in the sender sublist to be able to click on the arrow to have the listâ¦ and clicking on #senders does nothingâ¦. > > <image002.png> > > Thanks in advance for solving the issues, > > Cheers > Vincent > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 25, 2016