January 2016 - Pharo-dev - lists.pharo.org

Smalltalk Hub on Chrome
by Sean P. DeNigris June 28, 2016

June 28, 2016

I noticed sometimes sthub hangs forever on Chrome (Version 34.0.1847.116 on Mavericks), but if I open it alongside in Safari, it loads fine... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Smalltalk-Hub-on-Chrome-tp4755788.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

9 15

spotter: top search for senders and references
by Tudor Girba June 4, 2016

June 4, 2016

Hi, With the latest GT integration, we also integrated the search for senders and references from the first step. Here is a detailed explanation about it, including what we still want to do, how itâs done, and how to discover what else is around: http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

8 30

doing stupid things (image will become unusable)
by Nicolai Hess June 1, 2016

June 1, 2016

Object := nil you can evaluate that piece of code, but afterwards .... Opal checks for assignments to read only variables (method arguments for example) and signals an error if you try to modify those vars. But it does not check globals. Should all Globals (OCLiteralVariable with isGlobalVar == true) be read only ? or can we distinguish global vars and class bindings?

6 10

Some GT tool for this?
by Mariano Martinez Peck April 21, 2016

April 21, 2016

How many times have you tried to search a string as a comment of a commit in all the history? Myself: many many times. I know we need much better tools for that, store the history in a another way, provide a nicer API, etc etc. And I know there were topics about that. However, I would deeply appreciate a very short term solution for ease that. The model side is as simple as this: | packageName ancestry anscestors substring | packageName := 'MyPackageXX'. substring := 'whatever I want to search'. ancestry := (MCWorkingCopy allManagers detect: [:each | each packageName = packageName] ) ancestry. anscestors := ancestry withBreadthFirstAncestors select: [:each | each isKindOf: MCVersionInfo]. anscestors select: [ :each | each message includesSubstring: substring ] Do you think it's worth a simple UI tool? Custom inspector of MCAncestry? Cheers, -- Mariano http://marianopeck.wordpress.com

4 8

SessionManager (aka new startup / shutdown list manager) needs testers
by Christophe Demarey March 25, 2016

March 25, 2016

Hi, Guillermo, Pablo and I started to work on a new implementation for the image startup / shutdown list. The old implementation misses domain objects, polluted the SmalltalkImage class and introduced crazy dependencies to other packages. So, what is Session Manager? a replacement of the Session class (is now WorkingSession) a rewrite of startup / shutdown list with domain objects SessionManager: can create new sessions and manage categories. Also provide a facade to register new session handlers. Session manager provide sthe list of handlers by order of priority (categories order and categories priority) either for the startup or the shutdown, WorkingSession: unique object for the current smalltalk session (I.e. between a startup and a shutdown). On each image startup the current session is invalidated and a new session is created. Define how errors should be handled. Run the startup / shutdown process. SessionCategory: we defined some well known categories for startup / shutdown: system, network, GUI, tools and there is room to add user specific categories, It help to run the handler at the right time without caring about the whole order. and SessionHandlers: handleSession for a specific class or any other object. the shutdown list is now simply the startup list reversed we also refactored error handling at startup by using the UIManager and StartupUIManager. It allowed to remove ugly checks like #isInteractive, isHeadless in error handling methods and centralize that in UIManager. You can find an image with the new SessionManager in action here: https://ci.inria.fr/pharo-contribution/job/SessionManager/ As it is a critical piece of code, could you play / test it a bit before we integrate this new mechanism in the Pharo image? Regards, Christophe ps: Pharo tests pass ps2: There is still some code to clean / remove from the old startup management system.

6 13

[ANN] FFICHeaderExtractor first milestone (for early code reviewers) [WAS] Can OSProcess functionality be implemented using FFI instead of plugin?
by Mariano Martinez Peck March 18, 2016

March 18, 2016

Hi guys, OK, I have a first working version and so I wanted to share it with you. I have not yet the time to start writing the doc since I just finished the first pass on the code. Tomorrow I will start with the doc. But I thought some of you may be interested in taking a look even without formal "doc" (and some feedback/iteration may avoid re-writing docs..). If you have no clue what I am talking about, then this summary is for you: *----------* *When we use FFI to call a certain library it's quite common that we need to pass as argument certain constants (for example, SIGKILL to kill()). These constants are defined in C header files and can even change it's value in different paltforms. * *These constants also are sometimes defined by the C preprocessor and so there is not way to get those values from FFI. If you don't have the value of those constants, you cannot make the FFI call. * *----------* I have tested the tool in OSX and CentOS using latest Pharo 5.0. It won't work in Windows right now. As usual, all classes and methods have comments and there are enough tests. At the end, I decided the C program will output a very naive Smalltalk literal array kind of thingy. The tool then parses that output and directly creates a init method (which is compiled into the SharedPool class) for that platform which is then called automatically at startup (only if initialization is needed). As for real examples, I started to write constants for libc: signal.h (to use kill()) , wait.h (to use wait() famility), fcntl.h (to use ... xxx()) , and errno.h. You can take a look to the package 'FFICHeaderExtractor-LibC'. Note that for running the tests you need 'cc' findable by path in OSX and 'gcc' in Unix. To load the code in a latest Pharo 5.0, execute: Metacello new baseline: 'FFICHeaderExtractor'; repository: 'github://marianopeck/FFICHeaderExtractor:master/repository'; load. Any feedback is appreciated. I will start writing the doc now. BTW: Big thanks to Eliot Miranda which helped me answering noob questions and providing useful code and guidelines. Best, On Sat, Jan 23, 2016 at 1:12 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Denis, > > On Jan 23, 2016, at 7:30 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > > 2016-01-22 22:35 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> Let's measure this. Let's say we have 8 platforms (that's an >> underestimate, because different Linux distributions may have different >> values for certain constants), but 8, which is 4 basic platforms times 32- >> & 64-bits. We have Mac x86 32-bit, Mac x64 64-bit, Windows x86 >> 32-bit, Windows x64 64-bit, Linux x86 32-bit, Linux ARM 32-bit, Linux x64 >> 64-bit, and soon enough there will be more. Further, there may be >> different versions over time. >> >> So each of those initialization methods has >> - 1 slot for the global variable to be assigned >> - 1 slot for the literal value to assign to it >> - 3 bytes of bytecode per initialization for small methods, 4 for large >> methods. Let's say 4. >> >> So the overhead in 32-bits is 12 bytes per constant, and in 64-bits is 20 >> bytes. So the overhead per constant for all platforms is 96 bytes per >> constant in 32-bits and 160 bytes per constant for 64-bits. A full system >> with sockets, files, a database connexion etc could easily exceed 100 >> constants. I think it would be nearer 1000. So the overheads are in the >> 10- to 100-k byte range (100k ~= 0.5% of the image) on 32-bits. That's low >> but it's also pure overhead. Every GC has to visit them. Every senders >> and implementors has to visit them, but they offer nothing of value. >> Whereas the small parser for whatever notation is used to store the >> constants externally (if they are needed in a given deployment) has a small >> constant overhead; its simple code. >> >> Further, you still need the machinery to export the constants to be able >> to generate these initialization methods. If you've got the machinery and >> you don't need the methods why bother to generate the methods? >> >> As the Scots say, many a mickle makes a muckle. > > > Thank's Eliot for such detailed explanation. It makes sense. > But personally I prefer Smalltalk solution although Smalltalk itself is > pure overhead comparing to C. > > > I can see the draw of the pure Smalltalk. Simplicity and brows ability. > But imagine a tiny headless image deployed on containers, say 2mb. Now > 100kb of initialization code doesn't look so good :-). Anyway I'm beating > a dead horse. Mariano is generating initialization methods. > > > My question was raised by Mariano idea to save ston files in methods. I > think it can reduce problems which you described. > But then literal array syntax can be more suitable than ston. > > > I just want to be clear, I'm neutral about the notation used to export > info from the C file. Liberal array syntax, chunk source format, ston, > xml. It doesn't matter as long as it's convenient at expressing an > attribute dictionary from names to attributes such as value, size, offset. > Don't get hung up on the specific notation. If one were to go with the > external file the only real requirements are that it be reasonably compact > and quick to parse. That might kill xml but leave plenty of other > candidates. > > > _,,,^..^,,,_ (phone) > > -- Mariano http://marianopeck.wordpress.com

4 4

Rubric mutability issue in RubTextComposer binary search
by Aliaksei Syrel March 5, 2016

March 5, 2016

Hi, seems like there is a rather rare bug in Rubric. I opened an issue with explanation: https://pharo.fogbugz.com/f/cases/15153/Rubric-mutability-issue-in-RubTextC… Would be nice to fix it until release. It was caught in Spotter - as it heavily uses multithreading. Any suggestions are welcome if it is known :) Cheers, Alex

3 4

[ANN] Pharo bootstrap
by Christophe Demarey Feb. 29, 2016

Feb. 29, 2016

Hi all, In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it). This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore. With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-…. Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image). Christophe. ------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate: EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith: BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source SmallInteger>>no (source is Undeclared) UndefinedObject>>no (source is Undeclared) AbstractCompiler>>no (source is Undeclared) SmalltalkImage>>no (source is Undeclared) BlockClosure>>no (source is Undeclared) EvaluateCommandLineHandler>>no (source is Undeclared) EvaluateCommandLineHandler>>no (source is Undeclared) CommandLineHandler class>>no (source is Undeclared) BasicCommandLineHandler>>no (source is Undeclared) BasicCommandLineHandler>>no (source is Undeclared) PharoCommandLineHandler>>no (source is Undeclared) UIManager>>no (source is Undeclared) UndefinedObject>>no (source is Undeclared) CommandLineUIManager>>no (source is Undeclared) SmalltalkImage>>no (source is Undeclared) DelayMicrosecondScheduler>>no (source is Undeclared) BlockClosure>>no (source is Undeclared) SmalltalkImage>>no (source is Undeclared) WeakArray class>>no (source is Undeclared) ps: source cannot be displayed because there is no formatter available in the bootstrap

16 25

Differences Compiler vs. OpalCompiler (or parser)
by Nicolai Hess Feb. 24, 2016

Feb. 24, 2016

GTDummyExamples class d: anInteger <gtExample> <label: 'Dummy #d:, depends #c:'> <description: 'should raise an exception as the argument is not anInteger'> <depends: #c:> <raises: Literal constant expected -> MessageNotUnderstood> ^ 1 + anInteger The old Parser complains about the class name "MessageNotUnderstood" used as a pragma argument without being a string or symbol Opal does not complain Is Opals behavior intended ? >From squeaks bugtracker : http://bugs.squeak.org/view.php?id=7770 Cascading message sends to super. Compiler refuses to compile super initialize; setListProperties It looks like Opal would compile this to super initialize. super setListProperties. Intended ? Do we want to keep it? NBNativeCodeGen parseOptions: optionsArray uses association symbol -> block instead of block -> block for caseOf arguments. The old parser does not accept this.

4 11

Re: [Pharo-dev] [Pharo-users] World lastKeystroke and openInWorld: aPasteUpMorph
by Nicolai Hess Feb. 20, 2016

Feb. 20, 2016

2015-06-11 10:58 GMT+02:00 Markus Schlager <m.slg(a)gmx.de>: > issues opened > I added a fix for the broken lastkeystroke,but this will only work for the ActiveWorld/PasteUpMorph, not for any other PasteUpMorph. With the split of PasteUpMorph in PasteUpMorph and WorldMorph, and the change of keystroke handling (KMDispatcher), there is more to do to make this fully work again - but I don't want to reintroduce the old keyevent handling just to make this work again. I would like to remove all the keystroke handling from PasteUpMorph/WorldMorph and use only KMDispatcher. Maybe there is another(new) way to make this "lastKeystroke"-demo? You can open a transcript and enable the KMLog (KMLog setDebug. Transcript open) It will log all(!) keyevents and print the matching keymapping actions. Or something like this: |m| m := Morph new. m openInWorld. m takeKeyboardFocus. m on:($r ctrl) do:[ m color:Color red]. m on:($g ctrl) do:[ m color:Color green]. m on:($b ctrl) do:[ m color:Color blue]. This will open a morph that changes its color on ctrl+r/g/b So, maybe we can remove the whole "lastKeystroke" handling and make demos/examples like the above one? > > Markus > >

2 1