- Pharo-users - lists.pharo.org

Re: [Pharo-users] Using the new OSProcess still no Stdout string

by john pfersich

You want to use waitForCommand: instead of command:, like Transcript show: (PipeableOSProcess waitForCommand: 'whoami') output command: doesn't wait for output and is useful only for commands that don't return anything. It's kind of useless for anything that returns values. I haven't tried this on Pharo 5, I've gotten it to work on Pharo 4. On Friday, March 4, 2016, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I once reported a bug for OSProcess on MacOS > > > https://pharo.fogbugz.com/f/cases/16944/OSProcess-stdout-is-not-returned-ba… > > Still experience the same problem, is this suppose to be fixed with new > OSProcess ? > > >

March 5, 2016

Re: [Pharo-users] PharoLauncher eventual slowdown

by Ben Coman

On Sat, Mar 5, 2016 at 1:59 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-03-04 17:15 GMT+01:00 Ben Coman <btc(a)openinworld.com>: >> >> Hi Peter, I see you had this problem 12 months ago. >> >> http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-February/… >> >> What you can try is in development mode, closing the PharoLauncher >> window, nil out class variables and garbage collect, then check what >> instances remain of PharoLauncher classes. >> >> cheers -ben > > > > I use pharo launcer a lot (on windows) and I did not see any slow down. > But I don't use it for anything else then launching the images. > Do you notice the slow down by launching images or do you use the > PharoLauncher image for anything else? I think it was more when I was helping with PharoLauncher development and would close down/open it a lot. Since I've been mostly only using it I haven't noticed the problem. Or the root of that particular issue was fixed. cheers -ben > >> >> >> On Fri, Mar 4, 2016 at 6:42 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> > Yeah I saw that when he was in Prague (incidentally that's where my >> > launcher >> > slowdown started :)). >> > >> > I've removed write access and will report back in couple of days. :) >> > >> > Thanks, >> > Peter >> > >> > On Fri, Mar 4, 2016 at 11:24 AM, Damien Cassou <damien.cassou(a)inria.fr> >> > wrote: >> >> >> >> Hi Peter, >> >> >> >> Peter UhnÃ¡k <i.uhnak(a)gmail.com> writes: >> >> > I've been using Pharo Launcher for quite a while and problem that I >> >> > am >> >> > constantly encountering is that launching of it becomes slower and >> >> > slower. >> >> >> >> StÃ©phane, in CC, reported the same months ago on OS X. I don't know if >> >> StÃ©phane still experiences the problem. Could you please try to remove >> >> write access to the .image and .changes files? >> >> >> >> -- >> >> Damien Cassou >> >> http://damiencassou.seasidehosting.st >> >> >> >> "Success is the ability to go from one failure to another without >> >> losing enthusiasm." --Winston Churchill >> > >> > >> >

March 5, 2016

Re: [Pharo-users] Understanding Slang for building a compiler to C++

by Dimitris Chloupis

Thanks guys for the pointers, Clement I dont care about the VM my goal is not something like Slang but rather something that I will take a small piece of code in pharo lets say a few classes and convert it to C++ code that is human readable. But Esteban recommended to take a look at Slang anyway for what I want to create. My priority here is readable C++ code, rather than keeping the code as close to Pharo as possible. I know that compromises will have to be made, so no GC, static types etc. So I am looking into creating something that can take pharo code then the user adds annotations or extra syntax like types, pointers, manual memory managment, templates etc and then my compiler takes that and turns it to readable C++. I think this approach would be much easier for me to do instead of doing the hard work of trying to map Pharo to C++ which most likely is not possible since C++ even lacks simple reflection and of course will have to implement my own VM and my own GC . Essentially my goal is writing C++ with Pharo syntax or close to Pharo syntax. So people like me that want to take Pharo code and port it to C++ can do it easier than a manual rewrite. On Fri, Mar 4, 2016 at 10:36 PM Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > Hi Dimitris, > Pavel has extracted the code generator in this project > > http://smalltalkhub.com/#!/~PavelKrivanek/CCodeGenerator > > On Fri, Mar 4, 2016 at 9:06 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > >> Hey pharo experts I am interesting into studying how Slang works for >> making a compiler that takes pharo code and turns it to C++ code, my >> questions is where to find Slang , how to extract the code that compiles >> Slang to C and study it as an example for making my own compiler for C++. >> > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. >

March 4, 2016

Re: [Pharo-users] Making STON exportation lighter

by Mariano Martinez Peck

Not sure which is the reason of making it lighter, but you may also want to use a compressing stream so that the resulting stream is much smaller. On Thu, Mar 3, 2016 at 2:03 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > HI, > > There is a method in the class side of Object to override. This method > return all the instVar name that need to be serialized. You can > override it to store only the text. > > For example: > > Text class >>stonAllInstVarNames > "Override to encode my instances using a custom set of instance > variables or to define their order." > > ^ self allInstVarNames \ #runs > > On Thu, Mar 3, 2016 at 5:55 PM, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com> wrote: > > Hi, > > > > I'm using STON as my notebook storage file format for grafoscopio[1]. One > > example of such notebooks is at [2], but they grow large easily. That's > > because STON serialize a lot of information of each node. A snipped of > such > > info is something like [3], showed at the end of this mail. I remember > that > > someone told me about a way to store only the #string part of the Text > node, > > without any #runs or #values information in STON. How can this be done? > > > > Thanks, > > > > Offray > > > > Extra links and info: > > > > [1] http://mutabit.com/grafoscopio/index.en.html > > [2] > > > http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/Es/Tutoriales/tuto… > > > > =[3][STON code sniped]======= > > > > GrafoscopioNode { > > #header : > 'LecciÃ³n > > 1: Bienvenida', > > #headers : > > OrderedCollection [ ], > > #key : '', > > #body : Text { > > #string : > > '\"Hola!, Soy el profesor Stef. Debes querer que te ayude a aprender > > \rPharo. AsÃ que vamos a la primera lecciÃ³n: aprender a ejecutar cÃ³digo. > > \rPara ello hay varias opciones:\r - OpciÃ³n 1: Selecciona el texto > debajo, > > o coloca el cursor luego del punto, dale clic derecho y selecciona \'do > it > > (d)\'\r - OpciÃ³n 2: Haz click en el botÃ³n con el Ãcono de play que > aparece > > justo cerca a la esquina superior\r derecha de este > > panel\"\n\nPharoTutorial openPharoZenWorkspace \"no se qpoeadÃ±l > > aldskfjlasdf\"\r', > > #runs : > > RunArray { > > > > #runs : [ > > > > 421, > > > > 2, > > > > 13, > > > > 1, > > > > 21, > > > > 1, > > > > 1, > > > > 26, > > > > 1, > > > > 1, > > > > 1 > > > ], > > > > #values : [ > > > > [ > > > > TextColor { > > > > #color : Color { > > > > #rgb : 451328430, > > > > #alpha : 255 > > > > } > > > > }, > > > > TextFontChange { > > > > #fontNumber : 1 > > > > } > > > > ], > > > > [ > > > > TextColor { > > > > #color : Color { > > > > #rgb : 0, > > > > #cachedDepth : 32, > > > > #cachedBitPattern : Bitmap [ > > > > 4278190080 > > > > ], > > > > #alpha : 255 > > > > } > > > > }, > > > > @18 > > > > ], > > > > [ > > > > TextColor { > > > > #color : Color { > > > > #rgb : 512, > > > > #alpha : 255 > > > > } > > > > }, > > > > RubTextClassLink { > > > > #className : #PharoTutorial > > > > }, > > > > RubTextClassLink { > > > > #className : #PharoTutorial > > > > }, > > > > RubTextClassLink { > > > > #className : #PharoTutorial > > > > }, > > > > RubTextClassLink { > > > > #className : #PharoTutorial > > > > > > > > ================== > > > > > > -- > Cheers > Cyril Ferlicot > > -- Mariano http://marianopeck.wordpress.com

March 4, 2016

Re: [Pharo-users] Understanding Slang for building a compiler to C++

by Bernardo Ezequiel Contreras

Hi Dimitris, Pavel has extracted the code generator in this project http://smalltalkhub.com/#!/~PavelKrivanek/CCodeGenerator On Fri, Mar 4, 2016 at 9:06 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Hey pharo experts I am interesting into studying how Slang works for > making a compiler that takes pharo code and turns it to C++ code, my > questions is where to find Slang , how to extract the code that compiles > Slang to C and study it as an example for making my own compiler for C++. > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

March 4, 2016

[Pillar] Ascii doc

by Thibault ARLOING

Hi, Yann Dubois and me were working on an asciidoc exporter for Pillar, he is now ready and available in the development version of Pillar. We will be gratefull for any feedbacks, thanks Good evening Thibault Arloing

March 4, 2016

Re: [Pharo-users] Rubric docs

by Alexandre Bergel

Good question. Once you have an answer, feel free to write a short Help :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 4, 2016, at 3:50 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > the (new) code box in Nautilus has some visual cool stuff: > > <rubric.png> > â > my question is: is this documented somewhere? Can I mold it for my own purposes? > > Peter

March 4, 2016

Rubric docs

by Peter UhnÃ¡k

Hi, the (new) code box in Nautilus has some visual cool stuff: â my question is: is this documented somewhere? Can I mold it for my own purposes? Peter

March 4, 2016

Re: [Pharo-users] PharoLauncher eventual slowdown

by Nicolai Hess

2016-03-04 17:15 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > Hi Peter, I see you had this problem 12 months ago. > > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-February/… > > What you can try is in development mode, closing the PharoLauncher > window, nil out class variables and garbage collect, then check what > instances remain of PharoLauncher classes. > > cheers -ben > I use pharo launcer a lot (on windows) and I did not see any slow down. But I don't use it for anything else then launching the images. Do you notice the slow down by launching images or do you use the PharoLauncher image for anything else? > > On Fri, Mar 4, 2016 at 6:42 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Yeah I saw that when he was in Prague (incidentally that's where my > launcher > > slowdown started :)). > > > > I've removed write access and will report back in couple of days. :) > > > > Thanks, > > Peter > > > > On Fri, Mar 4, 2016 at 11:24 AM, Damien Cassou <damien.cassou(a)inria.fr> > > wrote: > >> > >> Hi Peter, > >> > >> Peter UhnÃ¡k <i.uhnak(a)gmail.com> writes: > >> > I've been using Pharo Launcher for quite a while and problem that I am > >> > constantly encountering is that launching of it becomes slower and > >> > slower. > >> > >> StÃ©phane, in CC, reported the same months ago on OS X. I don't know if > >> StÃ©phane still experiences the problem. Could you please try to remove > >> write access to the .image and .changes files? > >> > >> -- > >> Damien Cassou > >> http://damiencassou.seasidehosting.st > >> > >> "Success is the ability to go from one failure to another without > >> losing enthusiasm." --Winston Churchill > > > > > >

March 4, 2016

Re: [Pharo-users] Understanding Slang for building a compiler to C++

by ClÃ©ment Bera

Hello Dimitris, In the VMMaker packages you will find Slang. See the generator.image that you can build here: https://github.com/pharo-project/pharo-vm to get the package in Pharo. Slang is used exclusively for VM compilation and simulation. The package named 'VMMaker-Translation to C' does what you are looking for. It translates Smalltalk source code to Smalltalk AST, then Smalltalk AST to Slang AST, then perform some optimizations on Slang AST, then writes the C code. The slang AST is all the class with names starting with T in this package. The CCodeGenerator is the class responsible for C code generation from slang AST. A closed world assumption allows the generator to do inlining efficiently and compile to direct function call, hence C code generation of a single method can be done only by parsing all the slang method needed for C compilation. The closed world is defined according to different settings such as which memory manager or which jit back end is used. There are no polymorphism in the generated c code, though there are polymorphism in Slang, for example all the memory managers are polymorphic with each other, but you have to pick one of them for C compilation. Super sends acts as macro replacements. There are no such things as mapping Smalltalk classes to C++ classes, it's more about compiling a huge pack of functions all together. The other packages of VM Maker are related to the interpreter, the JIT, the Memory manager and the simulator. Code used exclusively for simulation or testing purpose can be Smalltalk, but most code here is in Slang. There are documentation about the VM in general but I don't think there is documentation specifically about slang itself. Slang is meant to compile the VM and only the VM, hence both projects are tied together. It does not feel like it's a good idea to extract the C code generator as some things were hacked in the generator to make VM compilation work, while the VM code was hacked to work with the generator. In fact, each time we want to do something that is not possible in the VM, we hack either the VM code or the slang generator depending on which solution implies the least time consumption over the next few years. You have to know that the Slang to C generation is, in my opinion, the worst code of the whole VM packages. This is the kind of script I use in Squeak to generate the C code for a single smalltalk method and check if everything is correct, I guess it works in Pharo, as you can see, the compilation process is dependent on VM compilation, as you have to precise which JIT and memory manager to use to define correctly the closed world that will be generated and hence what function you can call or inline : (Transcript show: [| sel vmm s cg | sel := #writeImageFileIO. vmm := (VMMaker forPlatform: 'Cross') interpreterClass: CoInterpreter"MT"; options: {#Cogit. Cogit chooseCogitClass name}, #(ObjectMemory Spur32BitCoMemoryManager "NewspeakVM true MULTIPLEBYTECODESETS true" SistaVM false). cg := [vmm buildCodeGeneratorForInterpreter] on: Notification do: [:ex| ex tag == #getVMMaker ifTrue: [ex resume: vmm] ifFalse: [ex pass]]. "cg breakSrcInlineSelector: #readHeapFromImageFile:dataBytes:; breakDestInlineSelector: sel; breakOnInline: false""true". cg vmClass preGenerationHook: cg. cg inferTypesForImplicitlyTypedVariablesAndMethods. cg retainMethods: { sel }. cg prepareMethods. ((sel beginsWith: 'bytecode') or: [sel endsWith: 'Bytecode']) ifTrue: [cg doBasicInlining: true] ifFalse: [cg doInlining: true]. s := ReadWriteStream on: String new. (cg methodNamed: sel) removeUnusedTempsAndNilIfRequiredIn: cg; halt; emitCCodeOn: s generator: cg. s contents] value) I'd recommend you to ask question about this topic on the VM mailing list ( http://lists.squeakfoundation.org/mailman/listinfo/vm-dev) because few people in the Pharo community have a good understanding of Slang, and the ones whodo are also on vm-dev. Have fun :-) 2016-03-04 13:06 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Hey pharo experts I am interesting into studying how Slang works for > making a compiler that takes pharo code and turns it to C++ code, my > questions is where to find Slang , how to extract the code that compiles > Slang to C and study it as an example for making my own compiler for C++. >

March 4, 2016