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

Re: [Pharo-dev] [issue tracker] 6 issue fixed in external package, needs to be pushed into pharo

by Marcus Denker

Now 8. > On 08 Oct 2015, at 09:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Re-Ping. Now we have 7 issues waiting. > >> On 05 Oct 2015, at 08:04, marcus.denker(a)inria.fr wrote: >> >> Hello Maintainers of externally managed packages, >> >> We have 6 cases that need your action to get the fix (which is fixed in the repo of the package) >> back into Pharo. >> >> I made a new filter so these cases are easy to find: >> >> https://pharo.fogbugz.com/f/filters/138/fixed-upstream >> >> Keep in mind that it is better to merge back sooner than later, especially trivialities. >> >> Marcus >

Oct. 8, 2015

Re: [Pharo-dev] Problems with a large block

by Eliot Miranda

Hi Nicolai, On Thu, Oct 8, 2015 at 12:09 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-10-08 1:30 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> Hi Nicolai, >> >> On Wed, Oct 7, 2015 at 2:13 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> >>> >>> 2015-10-07 16:49 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >>> >>>> >>>> > On 07 Oct 2015, at 15:49, Marco Naddeo <naddeo(a)di.unito.it> wrote: >>>> > >>>> > Hi, >>>> > >>>> > I have some problems with the large block at bottom: >>>> > >>>> > -sending the message argumentNames gives me an empty array #() >>>> > -sending the message sourceNode gives me a strange result and not a >>>> RBBlockNode, as I would expect >>>> > >>>> >>>> This happens already with: >>>> >>>> [ :h :s :v | | min chroma hdash X red green blue | ] sourceNode >>>> >>>> I will checkâ¦ it is a bug in the mapping pc -> AST. >>>> >>> >>> That's interesting, the way the pc is mapped to the AST (ir >>> instructionForPC: ) >>> takes the "length" of the instruction bytecode into account and the >>> length of a pushclosure includes >>> all bytes needed for the pushing the local temps (pushConstant nil. >>> pushConstant nil ....) >>> >>> But the startPC of a block context starts at the first push, not after, >>> that means >>> >>> self method sourceNodeForPC: self startpc - 1 >>> starts the search after the push closure bytecode but before any push >>> local temp byte code. >>> >>> Either we don't include the bytecodes for the "pushConstant:nil" in the >>> bytecode offset, or we start the search at >>> >>> self method sourceNodeForPC: self startpc - 1 + self numLocalTemps >>> >> >> No, no, no, no, no :-). >> > > I think I will always get confused by BlockClosure code at the bytecode > level :) > What exactly do you find confusing? The byte codes are simple if you read the right source. Perhaps you could talk with ClÃ©ment; he's local and understands the byte code set as well as I do. If you can't talk to him you could read the class comment of EncoderForV3PlusClosures in a Squeak 4.6 or 5.0 image, or the class comment of EncoderForSistaV1 in the BytecodeSets package on http://source.squeak.org/VMMaker. If you're confused by the scheme for closing over variables have you read my blog posts on the closure compiler? I wish you hadn't deleted this bit, it is "the truth": "*The PC in question is the pc of the block creation byte code. The startpc of a block is the first bytecode following the block creation byte code. That *includes* any pushConstant: nil byte codes establishing temps in the block. Instead, it is expected that "self method sourceNodeForPC: self startpc - 1" answers the same as "self method sourceNodeForPC: self blockCreationPC", where self blockCreationPC is the pc of the block's block creation bytecode.* *In Squeak we have* *BlockClosure>>blockCreationPC* * "Answer the pc for the bytecode that created the receuver."* * | method |* * method := self method.* * ^method encoderClass* * pcOfBlockCreationBytecodeForBlockStartingAt: startpc* * in: method* *This is because we support (as you will soon enough) different byte code sets so it is wrong to assume the size of the block creation bytecode is 4.* " > >> >> self method sourceNodeForPC: self startpc - 4 >> > > We already have this little heuristic > > instructionForPC: aPC > 0 to: -3 by: -1 do: [ :off | > (self firstInstructionMatching: [:ir | ir bytecodeOffset = (aPC - > off) ]) ifNotNil: [:it |^it]] > > AFAUI this 0 to -3 offset is used because we have 1,2,3 or 4 byte-length > bytecodes. > Well this will break down with the Sista byte code set because one could conceivably have 7 or 8 byte bytecoedes when one includes prefixes. In the Newspeak and Sista sets we extend the ranges of byte codes by allowing prefixes. Notionally the number of prefixes is unlimited but in practice we're using only one of each of the two prefix bytecodes Prefix A & Prefix B (currently E0 and E1 in all sets). But in the Sista set there is a field in the block creation byte code that reveals how many prefixes the byte code has so one can compute the actual start of the block creation byte code. i.e. EncoderForSistaV1 class>>pcOfBlockCreationBytecodeForBlockStartingAt: startpc in: method "Answer the pc of the push closure bytecode whose block starts at startpc in method. May need to back up to include extension bytecodes." "* 224 11100000 aaaaaaaa Extend A (Ext A = Ext A prev * 256 + Ext A) * 225 11100001 bbbbbbbb Extend B (Ext B = Ext B prev * 256 + Ext B) ** 250 11111010 eeiiikkk jjjjjjjj Push Closure Num Copied iii (+ExtA//16*8) Num Args kkk (+ ExtA\\16*8) BlockSize jjjjjjjj (+ExtB*256). ee = num extensions" | numExtensions | self assert: (method at: startpc - 3) = 250. numExtensions := (method at: startpc - 2) >> 6. ^startpc - 3 - (numExtensions * 2) and make sure that the compiler maps a block creation bytecode to the >> source node for the entire block. >> > > in the above code (instructionForPC) we try to find the instruction for > the pc (here the pc of the closure creation code), but I don't really > understand what > "bytecodeOffset" is, it looks like (bytecodeIndex+startPC), but for a > IRPushClosureCopy, it looks like the bytecodeIndex does include > the number of local temps resp. (numberOfLocalTemps times the > bytecodelength for pushConstant:nil). > Marcus, what is bytecodeOffset? Is it the distance from the first byte code or the distance from the first literal or...? The way to think about "self method sourceNodeForPC: self startpc - 1 + >> self numLocalTemps" not making sense is that a pc inside the block must map >> to a statement inside the block, not the block itself. >> > > Hm, I don't know :) > Why? I designed the closure byte code set so I'm telling you :-). It's safe to believe me. For example, an initial pushConstant: nil byte code in a block either establishes the first local temp in that block, or is an argument of a send in the block. In either case it refers to an element inside the block, not to the entire block itself. the thing that defines the entire block is the block creation byte code, which includes the span (the size of) the block's bytecodes. I chose to live with this annoying ambiguity because there were very few unused byte codes and I did;t want to use all of them for the closure byte code set. And I chose the closure architecture so I could write a faster VM than one that accessed temps directly in outer scopes (which I go into at length on my blog). HTH >> >> >>> >>> >>>> >>>> Marcus >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> > > -- _,,,^..^,,,_ best, Eliot

Oct. 8, 2015

Re: [Pharo-dev] Problems with a large block

by Nicolai Hess

2015-10-08 1:30 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Nicolai, > > On Wed, Oct 7, 2015 at 2:13 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> >> >> 2015-10-07 16:49 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >>> >>> > On 07 Oct 2015, at 15:49, Marco Naddeo <naddeo(a)di.unito.it> wrote: >>> > >>> > Hi, >>> > >>> > I have some problems with the large block at bottom: >>> > >>> > -sending the message argumentNames gives me an empty array #() >>> > -sending the message sourceNode gives me a strange result and not a >>> RBBlockNode, as I would expect >>> > >>> >>> This happens already with: >>> >>> [ :h :s :v | | min chroma hdash X red green blue | ] sourceNode >>> >>> I will checkâ¦ it is a bug in the mapping pc -> AST. >>> >> >> That's interesting, the way the pc is mapped to the AST (ir >> instructionForPC: ) >> takes the "length" of the instruction bytecode into account and the >> length of a pushclosure includes >> all bytes needed for the pushing the local temps (pushConstant nil. >> pushConstant nil ....) >> >> But the startPC of a block context starts at the first push, not after, >> that means >> >> self method sourceNodeForPC: self startpc - 1 >> starts the search after the push closure bytecode but before any push >> local temp byte code. >> >> Either we don't include the bytecodes for the "pushConstant:nil" in the >> bytecode offset, or we start the search at >> >> self method sourceNodeForPC: self startpc - 1 + self numLocalTemps >> > > No, no, no, no, no :-). > I think I will always get confused by BlockClosure code at the bytecode level :) > > self method sourceNodeForPC: self startpc - 4 > We already have this little heuristic instructionForPC: aPC 0 to: -3 by: -1 do: [ :off | (self firstInstructionMatching: [:ir | ir bytecodeOffset = (aPC - off) ]) ifNotNil: [:it |^it]] AFAUI this 0 to -3 offset is used because we have 1,2,3 or 4 byte-length bytecodes. > > and make sure that the compiler maps a block creation bytecode to the > source node for the entire block. > in the above code (instructionForPC) we try to find the instruction for the pc (here the pc of the closure creation code), but I don't really understand what "bytecodeOffset" is, it looks like (bytecodeIndex+startPC), but for a IRPushClosureCopy, it looks like the bytecodeIndex does include the number of local temps resp. (numberOfLocalTemps times the bytecodelength for pushConstant:nil). > > The way to think about "self method sourceNodeForPC: self startpc - 1 + > self numLocalTemps" not masking sense is that a pc inside the block must > map to a statement inside the block, not the block itself. > > Hm, I don't know :) > HTH > > >> >> >>> >>> Marcus >>> >>> >>> >>> >>> >>> >> > > > -- > _,,,^..^,,,_ > best, Eliot >

Oct. 8, 2015

Re: [Pharo-dev] [issue tracker] 6 issue fixed in external package, needs to be pushed into pharo

by Marcus Denker

Re-Ping. Now we have 7 issues waiting. > On 05 Oct 2015, at 08:04, marcus.denker(a)inria.fr wrote: > > Hello Maintainers of externally managed packages, > > We have 6 cases that need your action to get the fix (which is fixed in the repo of the package) > back into Pharo. > > I made a new filter so these cases are easy to find: > > https://pharo.fogbugz.com/f/filters/138/fixed-upstream > > Keep in mind that it is better to merge back sooner than later, especially trivialities. > > Marcus

Oct. 8, 2015

[pharo-project/pharo-core] 0c9b32: 50372

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0c9b32f314e4f089a8c054e7856b3946c996a81e https://github.com/pharo-project/pharo-core/commit/0c9b32f314e4f089a8c054e7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-10-08 (Thu, 08 Oct 2015) Changed paths: M Collections-Strings.package/String.class/instance/accessing/includesSubstring_.st M Nautilus-Tests.package/NautilusUITest.class/instance/initialization/setUp.st M Reflectivity.package/ReflectiveMethod.class/instance/evaluation/compileAndInstallCompiledMethod.st M Reflectivity.package/ReflectiveMethod.class/instance/evaluation/run_with_in_.st M ScriptLoader50.package/ScriptLoader.class/instance/accessing/diffServerRootString.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50371.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50372.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50371.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50372.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestions-Tests.package/SugsContextTest.class/instance/valid-context/testContextForNautilusItsANautilusContext.st Log Message: ----------- 50372 16737 fix all users of NautilusUI https://pharo.fogbugz.com/f/cases/16737 12354 includesSubstring: should return true when the argument is empty https://pharo.fogbugz.com/f/cases/12354 16738 Reflectivity: do not wrap primitives if there is no link https://pharo.fogbugz.com/f/cases/16738 16418 ScriptLoader>>diffServerRootString with Pharo 3 repo for Pharo 5? https://pharo.fogbugz.com/f/cases/16418 http://files.pharo.org/image/50/50372.zip

Oct. 8, 2015

[pharo-project/pharo-core]

by GitHub

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

Oct. 8, 2015

Fun fact with FastTable...

by Thierry Goubier

FTTableContainerMorph>>drawOn: is called more than once (more than twice?) in quick succession (for every display request?). So the whole rowSubviews loop is done multiple times for no reason, since the first one is already correct. Thierry

Oct. 8, 2015

Re: [Pharo-dev] [squeak-dev] Autonomous Shark-Monitoring Drone

by David T. Lewis

Sounds like an interesting and worthwhile thing to do. I'm not sure how much I can contribute, but if it turns out that there is a need for any VM plugins and/or OSProcess glue to make the thing work, I will happily volunteer for that. I don't mind buying some hardware (Rasperry Pi?) to work with, although that rubber shark may be a bit beyond my budget. Seriously, this is a good idea and it would be a lot of fun if we could make it work. Dave On Wed, Oct 07, 2015 at 08:54:55AM -0700, Eliot Miranda wrote: > Dear Friends and Colleagues, > > as you may know, Sharks, as apex predators, are vital to maintaining > healthy marine ecosystems, and at the same time, their populations are > plummeting due to human actions. It is estimated for example that the > population of pelagic oceanic white tip sharks is reducing by 17% per year > [1] and I've heard (can't find a reference) that populations in the eastern > indian/western pacific are at 1% of normal levels. Such reductions in > populations create "trophic cascades" that produce wide-ranging changes in > populations of different species all the way down the food chain [2]. And > the marine ecosystem is a key source of human nutrition; it comprises > between 13% and 17% of global human protein intake [3]. > > As you may also know, there is currently a shark attack crisis in New > South Wales [4]. While most people in the region oppose killing sharks in > response to the crisis, existing solutions, netting and culling reduce > those same threatened populations of sharks upon which the sustainability > of marine food supply d ecosystems depend [5], and are arguably ineffective > [6]. Apparently the most successful approach at avoiding attacks is the > use of human spotters, as used in Cape Town, where people in tall towers > scan the sea close to shore [6]. > > But please watch this Youtube video > <https://www.youtube.com/watch?v=q2U3gjwJfS4> [7] from Pismo Beach, > California. The shark is spotted at about 1:20 into the video. This > drone, a phantom 3, is sending live video back to the operators, who are > using remote control. What we can see from this video is that the point of > view of drones is far superior to that of spotters. > > My first thought is that autonomous drones could provide a cheap and > scalable solution to patrolling beaches to prevent shark attacks. I expect > that processors like the Pi 2 have easily enough processing power to both > plan and execute search patterns along beaches, and perform the image > recognition necessary to reliably detect potentially dangerous sharks. A > drone might also be able autonomously to visit surfers and swimmers near to > the shark and warn them, either by some signal such as flashing red LEDs or > an audible message (language issues notwithstanding). The drone would have > to be able to identify swimmers and surfers in the water (not easy; sharks > confuse seals and surfers all the time), but computing an optimal route to > visit suspected swimmers should be relatively easy :-). > > I imagine that sooner or later it will be possible to construct cheap > rugged solar powered docking/charging shelters that drones could depart > from and return to, to charge and shelter from the elements after patrols. > Satellite communications could provide status reports for maintenance. > > My second thought is that as a community, we probably have all the > necessary expertise to construct a working prototype that at least > demonstrates feasibility. Such a prototype would have to be able to fly > above the ocean along a beach under its own control for a useful period of > time, at least 15 minutes, and demonstrate that it can identify a shark in > the water (we could use a rubber shark > <https://www.youtube.com/watch?v=9dghbyBaQyI> for testing ;-) ). > > Our community includes people doing image recognition with the Pi, radio > control experts, users of 3D printers, and some exceptional programmers. > If a small, strong group could be formed with the relevant expertise we may > be able to develop a prototype in a short enough time frame to be > relevant. Of course, availability of time is a big issue. I couldn't > contribute more than a few hours a week. But nothing ventured, nothing > gained. So I'm writing this message to the Squeak and Pharo communities, > and bcc'ing a few friends I know that have relevant expertise to ask for > two things; first, for good information on scoping out the project, > possible technologies, power budgets, costs, what is available > off-the-shelf (both in hardware and known algorithms) and what we would > need to construct ourselves, and second, for volunteers. Who among us are > really excited by this project, have relevant expertise and are motivated > to make a contribution? > > > [1] www.sharkadvocates.org/cites_4sharks_owt_fact_sheet.pdf > [2] http://www.globalshark.ca/pressmaterial/cascading/fig1_web.pdf > [3] http://www.who.int/nutrition/topics/3_foodconsumption/en/index5.html > [4] http://www.bbc.com/news/world-australia-34398516 > [5] > http://www.theguardian.com/environment/2015/sep/29/shark-hit-australian-com… > [6] http://www.nonswsharkcull.net/latestnews/tag/shark_spotting/ > [7] https://www.youtube.com/watch?v=q2U3gjwJfS4 > > > > crazier ideas: > > Infra red cameras are becoming cheap and easily available. Species like > Great White and Bull Shark have elevated metabolisms, effectively they are > warm blooded, so these two facts may allow spotting at night. > > Sharks are extremely sensitive to electrical fields; maybe some kind of > transmitter could be fitted to a drone, e.g. via a wire suspended in the > water, that could generate a field that could direct the shark away from > swimmers > > _,,,^..^,,,_ > best, Eliot >

Oct. 8, 2015

[ANN]: Magritte: Extensible Reference Description Morph

by Sean P. DeNigris

For those not following the Magritte list. I scratched an itch I've been feeling for a long time using Magritte... Full details at https://github.com/magritte-metamodel/magritte/issues/28 There was not a viable control for the use case where you are choosing between several likely known options, but may also select an unknown object that was not part of the initial options. For example, when tagging people in a photos, you'd want to start with known people, but be able to add new people too. Here's a screencast: https://www.youtube.com/watch?v=dV9_Z12G2Y0 NB the completion menu appears in a seemingly random place. I guess this is a Pharo bug, but I'm currently only using the morph internally so I can live with it ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Magritte-Extensible-Reference-Description-Morph-t… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 8, 2015

Re: [Pharo-dev] [ANN]: AconcaguaAddOns

by Sean P. DeNigris

stepharo wrote > welcome back. Thanks! You guys have been busy :) I've given up on trying to go back through all the mail I missed... ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-AconcaguaAddOns-tp4820940p4854309.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 8, 2015