September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] [ANN] Lowtalk, a new Smalltalk dialect that could eventually replace Slang

by Ronie Salgado

Hello Jimmie, On ESUG I only presented it for the innovation award. There is no scientific paper on Lowtalk itself yet, because most of the work on this front end is recently. I am probably submitting. There is still the possibility on changing the syntax and some of mechanism that are used in Lowtalk, Currently I am showing what is possible to do. What do you believe the best mailing list to list ask questions at some > point in the future? This is a good question. Currently I do not know. This is an early work, and there is still a lot more to do. We now have to discuss about how to proceed. I have to discuss properly with Eliot about how to keep proceeding. I am reusing some of his techniques for implementing some parts such as the stack to context mapping, and immediates objects. Lowtalk is currently Pharo only, and it is completely standalone from the OpenSmalltalk VM. However, I am going to make a backend for Lowtalk that uses Lowcode to be able to use it inside the current image environment. Both use cases are interesting: - standalone executables for embedding and soft realtime (videogames). - keeping the current VM and reusing the in-image environment allows to use the full power of the Pharo/Squeak environment. In this case, Lowtalk can be used for getting a performance boost in numerical intensive software loops (e.g: matrix multiplication, typically an O(n^3) algorithm), without having to resort to the FFI for calling externally compiled C code. I want to use Lowtalk in Woden 2 exactly for the second use case. Currently in Woden 2 I am using the language described in the Lowcode paper. Because the type system introduces dependencies on the compilation order, it does not behave well with Monticello which I had to patch in Woden 2. With Lowtalk I am solving that problem by using standard text files, and multiple semantic analysis passes over the AST to define circular types lazily. for example: Structure named: #LinkedListNode slots: { #next => (LinkedListNode pointer). #value => (Void pointer) }. Best regards, Ronie 2017-09-05 17:02 GMT+02:00 Jimmie <jlhouchin(a)gmail.com>: > > Hello Ronie, > > I think this looks very interesting. I just downloaded your paper to read. > I look forward to seeing the video of your ESUG demonstration. > > What do you believe the best mailing list to list ask questions at some > point in the future? > > Thanks again for your work on this interesting project. > > Jimmie > > > > > On 08/30/2017 11:05 AM, Ronie Salgado wrote: > >> Hi All, >> >> I am finally glad to announce an initial version of my secret experiment, >> Lowtalk: https://github.com/ronsaldo/lowtalk >> >> Lowtalk is a new Smalltalk dialect that generates relocatable binary >> object code, that can be linked with any C program or used to generate a >> standalone executable with the C linker. I am designing Lowtalk as a >> language for video game developing, where performance and multi-threading >> support is important. The Lowtalk compiler is completely written in Pharo. >> >> The main features of Lowtalk are the following: >> - The compiler is actually a meta circular evaluator, whose features are >> used for bootstraping the Lowtalk kernel. >> - The Lowtalk object model, including the layout of the objects is >> defined in the language itself. >> - Direct interface with C. There is an almost 1:1 mapping between the >> Lowtalk native types and the C types. There is a syntax extension for >> calling C functions. >> -Support for real multi-threading. >> - The current object model uses automatic reference counting, which is >> slow, but makes supporting real multi-threading easier. >> - Immediates are based on the Spur object model. >> - Partial support for generating debugging information in the DWARF >> standard. It is possible to place breakpoints and get correct stack traces >> with gdb. >> >> Lowtalk is on the line of my work with Lowcode, and I am planning on >> making a Lowtalk backend that uses Lowcode. The Lowtalk type system is >> almost the same as the one that I described at the paper: Lowcode: >> Extending Pharo with C Types to Improve Performance >> >> I will make a video later, and a proper demonstration at ESUG. >> >> Best regards, >> Ronie >> > >

Sept. 5, 2017

Re: [Pharo-dev] ESUG Pharo GIT BOFs

by Chris Cunningham

BOF - Birds of a Feather Basically, people with the same interests. On Tue, Sep 5, 2017 at 2:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > I don't see Esteban's talk in the conference schedule. > > Also, what is BOF shortcut for? > > P > > On Tue, Sep 5, 2017 at 9:18 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Thursday after the talk of Esteban 16h45 >> Please pass the message and join. >> Stef >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> >

Sept. 5, 2017

Re: [Pharo-dev] ESUG Pharo GIT BOFs

by Stephane Ducasse

Yes this wonderful Google Calendar does not refresh the link The talk of Esteban is scheduled thursday after the afternoon break. Stef On Tue, Sep 5, 2017 at 11:47 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > I don't see Esteban's talk in the conference schedule. > > Also, what is BOF shortcut for? > > P > > On Tue, Sep 5, 2017 at 9:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> Thursday after the talk of Esteban 16h45 >> Please pass the message and join. >> Stef >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >

Sept. 5, 2017

Re: [Pharo-dev] ESUG Pharo GIT BOFs

by Peter UhnÃ¡k

I don't see Esteban's talk in the conference schedule. Also, what is BOF shortcut for? P On Tue, Sep 5, 2017 at 9:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thursday after the talk of Esteban 16h45 > Please pass the message and join. > Stef > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

Sept. 5, 2017

Re: [Pharo-dev] [ANN] Lowtalk, a new Smalltalk dialect that could eventually replace Slang

by Jimmie

Hello Ronie, I think this looks very interesting. I just downloaded your paper to read. I look forward to seeing the video of your ESUG demonstration. What do you believe the best mailing list to list ask questions at some point in the future? Thanks again for your work on this interesting project. Jimmie On 08/30/2017 11:05 AM, Ronie Salgado wrote: > Hi All, > > I am finally glad to announce an initial version of my secret > experiment, Lowtalk: https://github.com/ronsaldo/lowtalk > > Lowtalk is a new Smalltalk dialect that generates relocatable binary > object code, that can be linked with any C program or used to generate a > standalone executable with the C linker. I am designing Lowtalk as a > language for video game developing, where performance and > multi-threading support is important. The Lowtalk compiler is completely > written in Pharo. > > The main features of Lowtalk are the following: > - The compiler is actually a meta circular evaluator, whose features are > used for bootstraping the Lowtalk kernel. > - The Lowtalk object model, including the layout of the objects is > defined in the language itself. > - Direct interface with C. There is an almost 1:1 mapping between the > Lowtalk native types and the C types. There is a syntax extension for > calling C functions. > -Support for real multi-threading. > - The current object model uses automatic reference counting, which is > slow, but makes supporting real multi-threading easier. > - Immediates are based on the Spur object model. > - Partial support for generating debugging information in the DWARF > standard. It is possible to place breakpoints and get correct stack > traces with gdb. > > Lowtalk is on the line of my work with Lowcode, and I am planning on > making a Lowtalk backend that uses Lowcode. The Lowtalk type system is > almost the same as the one that I described at the paper: Lowcode: > Extending Pharo with C Types to Improve Performance > > I will make a video later, and a proper demonstration at ESUG. > > Best regards, > Ronie

Sept. 5, 2017

Re: [Pharo-dev] Pharo / Iceberg BOF at ESUG

by Stephane Ducasse

Sure! Let me know when. I can show bit where I need help :) and the next items on my todo list. Stef On Fri, Sep 1, 2017 at 12:35 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would also be interested in a Pillar BOF. > > Doru > > >> On Sep 1, 2017, at 11:43 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> May be wednesday afternoon the talks >> >> On Fri, Sep 1, 2017 at 9:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> +1 >>> >>> Doru >>> >>> >>>> On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> +1 :) >>>> >>>>> On 31 Aug 2017, at 20:11, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>> >>>>> Hi >>>>> >>>>> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG. >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> âLive like you mean it." >>> >>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "We are all great at making mistakes." > > > > > > > > >

Sept. 5, 2017

Pharo BOF at ESUG

by Stephane Ducasse

Thursday after the talk of Esteban 16h45 Please pass the message and join. Stef

Sept. 5, 2017

ESUG Pharo GIT BOFs

by StÃ©phane Ducasse

Thursday after the talk of Esteban 16h45 Please pass the message and join. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 5, 2017

Re: [Pharo-dev] The mooc is looking for forum moderators

by Stephane Ducasse

Thanks you! On Mon, Sep 4, 2017 at 7:37 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Can be around. > > I did the MOOC once. > > Phil, missing ESUG :-( > > On Mon, Sep 4, 2017 at 7:34 PM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> > wrote: >> >> Hi I would like to help too, if possible. >> >> On 2 September 2017 at 22:33, Rene Paul Mages (ramix) <pharo(a)rmages.com> >> wrote: >>> >>> >>> >>> Le 01/09/2017 Ã 11:40, Serge Stinckwich a Ã©crit : >>> > I should be able to help like last year. >>> >>> Count me also in the forum moderators team. >>> >>> -- >>> Amicalement. >>> Rene Paul Mages ( GnuPG_key 1024D/2CC455D9 ) >>> http://blog.pharo.fr >>> >> >> >> >> -- >> Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, >> ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. > >

Sept. 4, 2017

Re: [Pharo-dev] The mooc is looking for forum moderators

by phil＠highoctane.be

Can be around. I did the MOOC once. Phil, missing ESUG :-( On Mon, Sep 4, 2017 at 7:34 PM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Hi I would like to help too, if possible. > > On 2 September 2017 at 22:33, Rene Paul Mages (ramix) <pharo(a)rmages.com> > wrote: > >> >> >> Le 01/09/2017 Ã 11:40, Serge Stinckwich a Ã©crit : >> > I should be able to help like last year. >> >> Count me also in the forum moderators team. >> >> -- >> Amicalement. >> Rene Paul Mages ( GnuPG_key 1024D/2CC455D9 ) >> http://blog.pharo.fr >> >> > > > -- > Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, > ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº. >

Sept. 4, 2017