- Pharo-users - lists.pharo.org

Re: [Pharo-users] New compiler: variable and recursive bloc of code

by ClÃ©ment Bera

Hello, The additional assignment is not needed. You get a warning because the warning detection is approximate and sometimes raises warning whereas it should not, but if you proceed, it compiles fine. 2014-09-10 8:54 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Hello, > > I noticed this change described bellow and I just want to have > confirmation about it: > > The new Pharo 2.0 compiler need to have variable assigned with a value > before it used in a recursive bloc of code. Of course it is a bit > inelegant. Or is it something else and does it need to be reported? > > Thanks to let me know > > Hilaire > > For example this Dr. Geo code break in Pharo 2.0: > > | triangle c | > triangle := [:s1 :s2 :s3 :n | > c segment: s1 to: s2; > segment: s2 to: s3; > segment: s3 to: s1. > n > 0 ifTrue: > [triangle > value: s1 > value: (c middleOf: s1 and: s2) hide > value: (c middleOf: s1 and: s3) hide > value: n-1]. > [...] > ]. > > It must be changed to: > > | triangle c | > triangle := []. <= CHANGE HERE > triangle := [:s1 :s2 :s3 :n | > c segment: s1 to: s2; > segment: s2 to: s3; > segment: s3 to: s1. > n > 0 ifTrue: > [triangle > value: s1 > value: (c middleOf: s1 and: s2) hide > value: (c middleOf: s1 and: s3) hide > value: n-1]. > [...] > ]. > > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istao.drgeo.eu > > >

Sept. 10, 2014

New compiler: variable and recursive bloc of code

by Hilaire

Hello, I noticed this change described bellow and I just want to have confirmation about it: The new Pharo 2.0 compiler need to have variable assigned with a value before it used in a recursive bloc of code. Of course it is a bit inelegant. Or is it something else and does it need to be reported? Thanks to let me know Hilaire For example this Dr. Geo code break in Pharo 2.0: | triangle c | triangle := [:s1 :s2 :s3 :n | c segment: s1 to: s2; segment: s2 to: s3; segment: s3 to: s1. n > 0 ifTrue: [triangle value: s1 value: (c middleOf: s1 and: s2) hide value: (c middleOf: s1 and: s3) hide value: n-1]. [...] ]. It must be changed to: | triangle c | triangle := []. <= CHANGE HERE triangle := [:s1 :s2 :s3 :n | c segment: s1 to: s2; segment: s2 to: s3; segment: s3 to: s1. n > 0 ifTrue: [triangle value: s1 value: (c middleOf: s1 and: s2) hide value: (c middleOf: s1 and: s3) hide value: n-1]. [...] ]. -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Sept. 10, 2014

Re: [Pharo-users] Workshop on Visual Data Narratives using Roassal/Pharo in our local hackerspace in BogotÃ¡ Colombia

by Tudor Girba

Very nice initiative! Doru On Tue, Sep 9, 2014 at 9:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > This is excellent! > > Just to let you know, if you need to do a demo of Roassal, you have here > the video a an easy to do demo: https://vimeo.com/94724841 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 9, 2014, at 12:27 PM, Offray Vladimir Luna CÃ¡rdenas < > offray(a)riseup.net> wrote: > > Hi, > > This is just a short mail to let you know whats happening here on the > Pharo/Roassal front. We will be starting our workshops on what we I call > Visual Data Narratives. Details (in Spanish) here: > > http://hackbo.co/hackboweb/eventos/evento/338 > > Cheers, > > Offray > > ps: I will show the Moose outliner, in its alpha stage. Hopefully the > threads where I ask how to solve the problems will move a little more and > we will be able to integrate this to the workshops memories building. > > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 10, 2014

Re: [Pharo-users] Workshop on Visual Data Narratives using Roassal/Pharo in our local hackerspace in BogotÃ¡ Colombia

by Alexandre Bergel

This is excellent! Just to let you know, if you need to do a demo of Roassal, you have here the video a an easy to do demo: https://vimeo.com/94724841 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Sep 9, 2014, at 12:27 PM, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > Hi, > > This is just a short mail to let you know whats happening here on the Pharo/Roassal front. We will be starting our workshops on what we I call Visual Data Narratives. Details (in Spanish) here: > > http://hackbo.co/hackboweb/eventos/evento/338 > > Cheers, > > Offray > > ps: I will show the Moose outliner, in its alpha stage. Hopefully the threads where I ask how to solve the problems will move a little more and we will be able to integrate this to the workshops memories building. > >

Sept. 9, 2014

Re: [Pharo-users] Math Ontologie on Pharo 3.0

by Sven Van Caekenberghe

Check/read my mail again: I don't think it is the compiler (my tests show it is not), then it must be Monticello, in the sense that it treats its input stream (encoding) wrongly. On 09 Sep 2014, at 15:25, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > 2014-09-09 14:12 GMT+02:00 Alain Busser <alain.busser(a)gmail.com>: > Is this a reproducible case? http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz > > > Well I tried to merge that in the latest Pharo 4. > > With Opal I got the error 'unknown character' > > With the old compiler I got unmatched string quote. > > If it's French, could it be a ' ? > > It looks like a parser bug to me... > > > I hope not :-) > > Alain > > On Tue, Sep 9, 2014 at 5:43 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > What kind of bug do you have with accent ? Do you have a stack trace ? > > More importantly, can you give us a reproducible case ? I will investigate tomorrow if you have a reproducible case to check if this is due to Opal. > > It may also be recent changes related to fonts. > > 2014-09-08 21:07 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I don't think it is related to Opal: I made a test class with an instance variable, accessor and class comment with accents - which I can file out and file in: > > > > > > > > I tested in 3.0 and 4.0 > > The problem might be with Monticello. > > > On 08 Sep 2014, at 20:05, Hilaire <hilaire(a)drgeo.eu> wrote: > > > Oh, by the way, it looks like the accents are on the instance variable names. > > > > I edited the subject to not pollute the original discussion thread. > > > > Hilaire > > > > Le 08/09/2014 20:01, Hilaire a Ã©crit : > >> Marcus, > >> > >> Alain's MathOntologie package provide Classes and Messages with French > >> accent, to ease the understanding of programming to high school students. > >> I am suspecting the new compiler or something related does not accepted > >> accented caracters or something different to ASCII. > >> > >> Alain, in your package I noted the sources is not utf-8 but iso-8859-15 > >> (8 bits), I converted it to utf-8 and tried to get it loaded in Pharo3, > >> but still accent characters caused problem, see screenshot. > >> > >> Enclosed source file utf-8 converted and improper imported source code > >> with accented variable name. > >> > >> Hilaire > >> > >> Le 08/09/2014 12:18, Alain Busser a Ã©crit : > >>> Hi, > >>> > >>> I don't know if it is related but I have problems importing french files > >>> inside Pharo 3: Anytime when there is an accentuated character there is > >>> an error, and the file is not imported. Even if the character is a quote > >>> inside double quotes (like in "it don't work") there is an error > >>> message. Right now I can't import MathsOntologie > >>> (http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz) > >>> > >>> into Pharo 3 and I have to go on developing it in Pharo 1.4... > >>> > >>> Alain > >>> > >> > >> > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istao.drgeo.eu > > > > > > > > >

Sept. 9, 2014

Workshop on Visual Data Narratives using Roassal/Pharo in our local hackerspace in BogotÃ¡ Colombia

by Offray Vladimir Luna CÃ¡rdenas

Hi, This is just a short mail to let you know whats happening here on the Pharo/Roassal front. We will be starting our workshops on what we I call Visual Data Narratives. Details (in Spanish) here: http://hackbo.co/hackboweb/eventos/evento/338 Cheers, Offray ps: I will show the Moose outliner, in its alpha stage. Hopefully the threads where I ask how to solve the problems will move a little more and we will be able to integrate this to the workshops memories building.

Sept. 9, 2014

Re: [Pharo-users] FFI signatures

by Annick Fron

If I have ulong ulong long long ulong should I look in unsignedLongAt: 1 5 9 13 17 (with an increment of 4) ?? Le 9 sept. 2014 Ã 15:43, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > it doesnât really matters. > what you need to be sure for alien is that you have an âevaluatorâ for that callback. > > for example, the > > exampleCqsort > > uses this callback: > > int (*)(const void *, const void *) > > so, in âCallbackâ instance side, you can find this definition: > > voidstarvoidstarRetint: callbackContext sp: spAlien > <signature: 'int (*)(const void *, const void *)' abi: 'IA32'> > ^callbackContext wordResult: > (block > value: (Alien forPointer: (spAlien unsignedLongAt: 1)) > value: (Alien forPointer: (spAlien unsignedLongAt: 5))) > > So, you need to add a method extension, something like: > > ulongulongRetulong: callbackContext sp: spAlien > <signature: âulong (*)(ulong, ulong)' abi: 'IA32'> > ^callbackContext wordResult: > (block > value: (spAlien unsignedLongAt: 1) > value: (spAlien unsignedLongAt: 5)) > > then you can declare your callback something like: > > cb := Callback > signature: 'ulong (*)(ulong, ulong)' > block: [ :arg1 :arg2 | ... ]. > > that has to work :) > > yes, is pretty complicated, and yes, you need to do a method for each kind of different signature you want to use. > but well, is the way it works now :) > > Esteban > > > On 09 Sep 2014, at 12:00, Annick Fron <list(a)afceurope.com> wrote: > >> What signature should I use for a callback ? >> âulongâ does not seem to work >> >> Annick >

Sept. 9, 2014

Re: [Pharo-users] Gettext with pharo 3 and seaside 3.1.2

by Hilaire

Absolutely right. I open a ticket for Alain https://pharo.fogbugz.com/f/cases/13980/Math-Ontologie-on-Pharo-3-0. Alain I suggest you get your hand in the Pharo bug tracker (http://bugs.pharo.org) and create yourself an account[1] there to comment and to report additional problem you may meet. [1] https://pharo.fogbugz.com/default.asp?W41 Le 09/09/2014 09:56, Marcus Denker a Ã©crit : > I will have a look and checkâ¦ (with the first goal to add an issue tracker entry for it) > On 08 Sep 2014, at 20:01, Hilaire<hilaire(a)drgeo.eu> wrote: -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Sept. 9, 2014

Re: [Pharo-users] Gettext with pharo 3 and seaside 3.1.2

by Hilaire

Absolutely right. I open a ticket for Alain https://pharo.fogbugz.com/f/cases/13980/Math-Ontologie-on-Pharo-3-0. Alain I suggest you get your hand in the Pharo bug tracker (http://bugs.pharo.org) and create yourself an account[1] there to comment and to report additional problem you may meet. [1] https://pharo.fogbugz.com/default.asp?W41 Le 09/09/2014 09:56, Marcus Denker a Ã©crit : > I will have a look and checkâ¦ (with the first goal to add an issue tracker entry for it) > On 08 Sep 2014, at 20:01, Hilaire<hilaire-QBJRSr1f4Ts(a)public.gmane.org> wrote: -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Sept. 9, 2014

Re: [Pharo-users] FFI signatures

by Esteban Lorenzano

it doesnât really matters. what you need to be sure for alien is that you have an âevaluatorâ for that callback. for example, the exampleCqsort uses this callback: int (*)(const void *, const void *) so, in âCallbackâ instance side, you can find this definition: voidstarvoidstarRetint: callbackContext sp: spAlien <signature: 'int (*)(const void *, const void *)' abi: 'IA32'> ^callbackContext wordResult: (block value: (Alien forPointer: (spAlien unsignedLongAt: 1)) value: (Alien forPointer: (spAlien unsignedLongAt: 5))) So, you need to add a method extension, something like: ulongulongRetulong: callbackContext sp: spAlien <signature: âulong (*)(ulong, ulong)' abi: 'IA32'> ^callbackContext wordResult: (block value: (spAlien unsignedLongAt: 1) value: (spAlien unsignedLongAt: 5)) then you can declare your callback something like: cb := Callback signature: 'ulong (*)(ulong, ulong)' block: [ :arg1 :arg2 | ... ]. that has to work :) yes, is pretty complicated, and yes, you need to do a method for each kind of different signature you want to use. but well, is the way it works now :) Esteban On 09 Sep 2014, at 12:00, Annick Fron <list(a)afceurope.com> wrote: > What signature should I use for a callback ? > âulongâ does not seem to work > > Annick

Sept. 9, 2014