- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Estimating the amount of change between Pharo 2.0 and 3.0

by btc＠openinworld.com

Pharo4Stef wrote: > Why? The tests are green. > When you change a complete compiler and AST then it is a lot of changes. > Then each time you changes a comment you change the timestamp soâ¦.. > Now 30 is stable since months. > > Stef > > PS: you know what is frightening is when you have a bug that arrives only after 2 weeks on heavy charged servers. > We got that in the past and the changes producing it when just a couple of lines. > So size is not a good predictor. > > What is frightening is the _ability_ of you guys to keep the system running each day as you make that amount of change :)

Feb. 22, 2014

Log of the february dev meeting

by Pharo4Stef

HI guys we did not have a full team meeting since nov so here is the log of the one feb 2014. 17 February 2014 TODO for 3.0 ââââââ - [todo] 17 issues left - [todo] Rpackage - [todo] classBuilder - [todo] VM - [todo] new pharo web sites - [todo] pharo list of changes - [no progress] OPAL methods withoutsource stalled unclear who is creating method without source. - [Todo ] SmalltalkInbox for projects - [Todo] Web site Pharodoc web site Association - [30] MetacelloRepository Todo for 40 âââââ - [40] NativeBoost on PharoS - [40] Kill Package Info - Rpackage iteration under way - [40] TxModel - (done) refactoring immutable position selection - (done) visual is working - scrolling should be added - (done) page up down should be added - morph widget - finish - (done) Study Rubric - [40] NewInterpreter NewSpec interpreter two days of work should be integrated in this iteration - [40] bugs from the image - [40] NativeBoost with new ASMJIT version - [40] New look and feel - November - [40] SystemEvents - [40] Display VM Guile and Esteban are killing globals Stef

Feb. 22, 2014

Re: [Pharo-dev] Animation by Stepping

by Pharo4Stef

Jeff have a look at Viva in http://smalltalkhub.com/#!/~StephaneDucasse/PetitsBazars/ This is a first core frameworks that igor developed based on his previous C++ experiments. Stef

Feb. 22, 2014

Re: [Pharo-dev] Estimating the amount of change between Pharo 2.0 and 3.0

by Pharo4Stef

Why? The tests are green. When you change a complete compiler and AST then it is a lot of changes. Then each time you changes a comment you change the timestamp soâ¦.. Now 30 is stable since months. Stef PS: you know what is frightening is when you have a bug that arrives only after 2 weeks on heavy charged servers. We got that in the past and the changes producing it when just a couple of lines. So size is not a good predictor.

Feb. 22, 2014

Back to the mailing-list

by Pharo4Stef

Hi guys I decided to stop my retreat and be back to the mailing-list. Iâm preparing some actions that I want to discuss with you. Stef

Feb. 22, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by btc＠openinworld.com

Feb. 22, 2014

Re: [Pharo-dev] Morphic UI designer

by Stephan Eggermont

At the moment I'm moving, so I have very little time to do something about it. Current state is described in a thread from end of last year: http://forum.world.st/have-a-question-for-morphic-Designer-in-pharo-td47313… Stephan

Feb. 21, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by GÃ¶ran Krampe

Hey! On 02/21/2014 06:50 PM, Ronie Salgado wrote: > Hi there!, > > It is great to hear that it is being useful. Currently I am taking some > vacations, so I will probably be without Internet access for some days. [SNIP] > I took that kind of approach because it gives more flexibility, but it > provides probably a reduced performance in comparison with placing the > callouts directly in the wrapped classes. Some people that saw this when > developing this did not like this approach. Yeah, I can see what you mean - and I think that's just fine. One bit tricky problem: there are classes generated starting with lower case. That doesn't fly :) Also, LF instead of CRs after signatures makes NB barf when parsing. That was easily solved with a global tr '\n' '\r' of course, the class naming is a bit harder - need to go to the source. I can see if I can find that one :) regards, GÃ¶ran PS. Tried wrapping Nanomsg.org today, got so far as to start running test code - but then it fails creating a socket - not sure why, might not be your fault at all actually :) When it works I will blog about it.

Feb. 21, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by Alexandre Bergel

Really impressive Ronie!! Alexandre > Le 21-02-2014 Ã 12:50, Ronie Salgado <roniesalg(a)gmail.com> a Ã©crit : > > Hi there!, > > It is great to hear that it is being useful. Currently I am taking some vacations, so I will probably be without Internet access for some days. > Currently the most missing parts are documentation, which I am going to write when having some time. > > Here are some early details, before I start properly documenting them: > Â·This is heavily based in the C# bindings. There are additional typemaps such as nbtype, nbin and nbout. They are similar to the cstype, csin and csout typemaps presents the C# generator. > Â·They are two Smalltalk class and some common superclasses generated. One Smalltalk class contains all the NB-FFI callout methods, another contains wrappers for all the global C/C++ stuff. > Â·For each C++ a Smalltalk class is generated. > Â·The common superclass provides a destroy method for destroying an object. > Â·The extra overhead in new are to register properly with the GC. > Â·The C pointer is wrapped in a reference object that contains things for properly interact with the GC and destroying C++ object avoiding crashing the VM. > > Swig usually makes some kind of opaque type for some pointers. If they are intended to be an Array, maybe some extra typemaps has to be added. More information about typemaps is on the SWIG manual. > > I took that kind of approach because it gives more flexibility, but it provides probably a reduced performance in comparison with placing the callouts directly in the wrapped classes. Some people that saw this when developing this did not like this approach. > > I will document all of this more properly later, but I have to go now because I am in a hurry. > > Best regards, > Ronie Salgado > > > 2014-02-21 7:16 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> Excellent!!!! >> >> That's really a missing block coming to life! >> >> I'll try it this weekend on my Linux system. >> >> Phil >> >> >> >>> On Fri, Feb 21, 2014 at 10:24 AM, GÃ¶ran Krampe <goran(a)krampe.se> wrote: >>> Hi all! >>> >>>> On 01/22/2014 09:25 PM, Ronie Salgado wrote: >>>> I started working on extending SWIG to generate bindings for NativeBoost >>>> FFI, using as a reference the C# binding generator. I am committing my >>>> work on this into https://github.com/ronsaldo/swig/ . >>> >>> Just wanted to report that this stuff WORKS :) >>> >>> * I cloned down Ronie's SWIG. Did the autogen.sh, ./configure, make, make install dance. >>> * I went into Examples/ruby/value and: >>> * Changed module name to "Example" (instead of "example") >>> * Ran: swig -pharo example.i (produces C code and Example.st) >>> * Compile: gcc -m32 -c -fpic -fPIC example_wrap.c example.c >>> * Link: gcc -m32 -shared example.o example_wrap.o -o Example.so >>> * Then I filed in Example.st into Pharo 2.0, and put Example.so in the directory where I started the pharo VM. >>> >>> And well, after fixing some buglets (if you want to recreate this, email me or ask here) it works! I added a little test class for fun. >>> >>> Fantastic stuff! Sure, not complete by any means, but hey, it worked and not a single VM crash while playing with it. Ronie - good work! >>> >>> If you are on a Linux, I attached these two files. File into Pharo 2.0, open TestRunner and run ExampleTest. >>> >>> regards, GÃ¶ran >

Feb. 21, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by Ronie Salgado

Hi there!, It is great to hear that it is being useful. Currently I am taking some vacations, so I will probably be without Internet access for some days. Currently the most missing parts are documentation, which I am going to write when having some time. Here are some early details, before I start properly documenting them: Â·This is heavily based in the C# bindings. There are additional typemaps such as nbtype, nbin and nbout. They are similar to the cstype, csin and csout typemaps presents the C# generator. Â·They are two Smalltalk class and some common superclasses generated. One Smalltalk class contains all the NB-FFI callout methods, another contains wrappers for all the global C/C++ stuff. Â·For each C++ a Smalltalk class is generated. Â·The common superclass provides a destroy method for destroying an object. Â·The extra overhead in new are to register properly with the GC. Â·The C pointer is wrapped in a reference object that contains things for properly interact with the GC and destroying C++ object avoiding crashing the VM. Swig usually makes some kind of opaque type for some pointers. If they are intended to be an Array, maybe some extra typemaps has to be added. More information about typemaps is on the SWIG manual. I took that kind of approach because it gives more flexibility, but it provides probably a reduced performance in comparison with placing the callouts directly in the wrapped classes. Some people that saw this when developing this did not like this approach. I will document all of this more properly later, but I have to go now because I am in a hurry. Best regards, Ronie Salgado 2014-02-21 7:16 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Excellent!!!! > > That's really a missing block coming to life! > > I'll try it this weekend on my Linux system. > > Phil > > > > On Fri, Feb 21, 2014 at 10:24 AM, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > >> Hi all! >> >> On 01/22/2014 09:25 PM, Ronie Salgado wrote: >> >>> I started working on extending SWIG to generate bindings for NativeBoost >>> FFI, using as a reference the C# binding generator. I am committing my >>> work on this into https://github.com/ronsaldo/swig/ . >>> >> >> Just wanted to report that this stuff WORKS :) >> >> * I cloned down Ronie's SWIG. Did the autogen.sh, ./configure, make, make >> install dance. >> * I went into Examples/ruby/value and: >> * Changed module name to "Example" (instead of "example") >> * Ran: swig -pharo example.i (produces C code and Example.st) >> * Compile: gcc -m32 -c -fpic -fPIC example_wrap.c example.c >> * Link: gcc -m32 -shared example.o example_wrap.o -o Example.so >> * Then I filed in Example.st into Pharo 2.0, and put Example.so in the >> directory where I started the pharo VM. >> >> And well, after fixing some buglets (if you want to recreate this, email >> me or ask here) it works! I added a little test class for fun. >> >> Fantastic stuff! Sure, not complete by any means, but hey, it worked and >> not a single VM crash while playing with it. Ronie - good work! >> >> If you are on a Linux, I attached these two files. File into Pharo 2.0, >> open TestRunner and run ExampleTest. >> >> regards, GÃ¶ran >> > >

Feb. 21, 2014