- Pharo-users - lists.pharo.org

Re: [Pharo-users] eval from the linux commandline

by Alistair Grant

On Sun, 24 Mar 2019 at 00:54, test email <steveeq1(a)gmail.com> wrote: > > i need to eval an object from my linux commandline. I understand that clap-st is able to do this, but I can't seem to import it into pharo7, I suppose because of compatability reasons. Clap is now part of the base image, so you should be able to just download the latest image and use it "out of the box". Cheers, Alistair

March 24, 2019

Re: [Pharo-users] eval from the linux commandline

by K K Subbu

On 24/03/19 5:23 AM, test email wrote: > i need to eval an object from my linux commandline. I understand that > clap-st is able to do this, but I can't seem to import it into > pharo7, I suppose because of compatability reasons. > > Someone sent me this, but I can't seem to replicate the help screen. > Is it because I'm on linux and he's on mac? What exactly are you trying to evaluate? For simple expressions, I use: $ ./pharo Pharo.image eval 20 factorial 2432902008176640000 $ alias p='./pharo Pharo.image eval' $ p Morph allSuperclasses an OrderedCollection(Object ProtoObject) $ echo \'hello\' , \' world\' >hello.st $ p $(< hello.st) 'hello world' $ HTH .. Subbu

March 24, 2019

how to get out of this mess

by Roelof Wobben

Hello, I tried another way to solve this but the code is a mess now. I can update a record but the record is not updated. And I have to do a lot of the same steps for every team. Anyone who can help me to get out of this mess. Code so far:Â https://github.com/RoelofWobben/tournament Roelof

March 24, 2019

Re: [Pharo-users] [Pharo-dev] How to manage your code with Iceberg

by ducasse

We will add patterns of management. I would like to discuss about releaser at Pharodays :) Stef > On 24 Mar 2019, at 15:21, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Nice work! And very useful for newcomers, too :) > > Doru > >> On Mar 24, 2019, at 10:22 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hi >> >> I'm happy to announce a new booklet (soon to be released) on how to manage code with Iceberg. We plan to discuss management patterns in the future. >> >> https://github.com/SquareBracketAssociates/Booklet-ManagingCode >> >> Stef and Guille >> >> -------------------------------------------- >> 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 >> > > -- > www.feenk.com > > "Presenting is storytelling." > >

March 24, 2019

Re: [Pharo-users] ZnURL and parsing URL with diacritics

by PBKResearch

Well it didn't take long to find a potential problem in what I wrote, at least as a general solution. If the input string contains something which has already been percent encoded, it will re-encode the percent signs. In this case, decoding will recover the once-encoded version, but we need to decode twice to recover the original text. Any web site receiving this version will almost certainly decode once only, and so will not see the right details. The solution is simple - just include the percent sign in the list of excluded characters in the third line, so it becomes: url asString do: [ :ch|(':/?%' includes: ch ) -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of PBKResearch Sent: 24 March 2019 12:11 To: 'Any question about pharo is welcome' <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] ZnURL and parsing URL with diacritics Sean, Sven Thinking about this, I have found a simple (maybe too simple) way round it. The obvious first approach is to apply 'urlEncoded' to the received url string, but this fails because it also encodes the slashes and other segment dividers. A simple-minded approach is to scan the received string, copy the slashes and other segment dividers unchanged and percent encode everything else. I cobbled together the following in a playground, but it could easily be turned into a method in String class. urlEncodedSegments := [ :url||outStream| outStream := String new writeStream. url asString do: [ :ch|(':/?' includes: ch ) ifTrue: [ outStream nextPut: ch ] ifFalse:[outStream nextPutAll: ch asString urlEncoded ] ]. outStream contents]. urlEncodedSegments value: 'https://fr.wiktionary.org/wiki/pÃ©ripÃ©tie' => https://fr.wiktionary.org/wiki/p%C3%A9rip%C3%A9tie This may fail if a slash can occur in a url other than as a segment divider. I am not sure if this is possible - could there be some sort of escaped slash within a segment? Anyway, if the received url strings are well-behaved, apart from the diacritics, this approach could be used as a hack for Sean's problem. HTH Peter Kenny Note to Sven: The comment to String>>urlEncoded says: ' This is an encoding where characters that are illegal in a URL are escaped.' Slashes are escaped but are quite legal. Should the comment be changed, or the method? -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe Sent: 23 March 2019 20:03 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] ZnURL and parsing URL with diacritics > On 23 Mar 2019, at 20:53, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Peter Kenny wrote >> And when I inspect the result, it is the address of a non-existent >> file in my image directory. > > Ah, no. I see the same result. By "worked" I meant that it created a > URL that safari accepted, but I see now it's not the same as correctly > parsing it. > > > Peter Kenny wrote >> Incidentally, I tried the other trick Sven cites in the same thread. >> The same url as above can be written: >> 'https://fr.wiktionary.org/wiki' asUrl / 'pÃ©ripÃ©tie'. > > Yes, this works if you are assembling the URL, but several people > presented the use case of processing URLs from elsewhere, leaving one > in a chicken-and-egg situation where one can't parse due to the > diacritics and can't escape the diacritics (i.e. without incorrectly > escaping other things) without parsing :/ Yes, that is pretty close to a catch 22. Strictly speaking, such URLs are incorrect and can't be parsed. I do understand that sometimes these URLs occur in the wild, but again, strictly speaking they are in error. The fact that browser search boxes accept them is a service on top of the strict URL syntax, I am not 100% sure how they do it, but it probably involves a lot of heuristics and trial and error. The parser of ZnUrl is just 3 to 4 methods. There is nothing preventing somebody from making a new ZnLoseUrlParser, but it won't be easy. > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

March 24, 2019

Re: [Pharo-users] ZnURL and parsing URL with diacritics

by PBKResearch

Sean, Sven Thinking about this, I have found a simple (maybe too simple) way round it. The obvious first approach is to apply 'urlEncoded' to the received url string, but this fails because it also encodes the slashes and other segment dividers. A simple-minded approach is to scan the received string, copy the slashes and other segment dividers unchanged and percent encode everything else. I cobbled together the following in a playground, but it could easily be turned into a method in String class. urlEncodedSegments := [ :url||outStream| outStream := String new writeStream. url asString do: [ :ch|(':/?' includes: ch ) ifTrue: [ outStream nextPut: ch ] ifFalse:[outStream nextPutAll: ch asString urlEncoded ] ]. outStream contents]. urlEncodedSegments value: 'https://fr.wiktionary.org/wiki/pÃ©ripÃ©tie' => https://fr.wiktionary.org/wiki/p%C3%A9rip%C3%A9tie This may fail if a slash can occur in a url other than as a segment divider. I am not sure if this is possible - could there be some sort of escaped slash within a segment? Anyway, if the received url strings are well-behaved, apart from the diacritics, this approach could be used as a hack for Sean's problem. HTH Peter Kenny Note to Sven: The comment to String>>urlEncoded says: ' This is an encoding where characters that are illegal in a URL are escaped.' Slashes are escaped but are quite legal. Should the comment be changed, or the method? -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe Sent: 23 March 2019 20:03 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] ZnURL and parsing URL with diacritics > On 23 Mar 2019, at 20:53, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Peter Kenny wrote >> And when I inspect the result, it is the address of a non-existent >> file in my image directory. > > Ah, no. I see the same result. By "worked" I meant that it created a > URL that safari accepted, but I see now it's not the same as correctly > parsing it. > > > Peter Kenny wrote >> Incidentally, I tried the other trick Sven cites in the same thread. >> The same url as above can be written: >> 'https://fr.wiktionary.org/wiki' asUrl / 'pÃ©ripÃ©tie'. > > Yes, this works if you are assembling the URL, but several people > presented the use case of processing URLs from elsewhere, leaving one > in a chicken-and-egg situation where one can't parse due to the > diacritics and can't escape the diacritics (i.e. without incorrectly > escaping other things) without parsing :/ Yes, that is pretty close to a catch 22. Strictly speaking, such URLs are incorrect and can't be parsed. I do understand that sometimes these URLs occur in the wild, but again, strictly speaking they are in error. The fact that browser search boxes accept them is a service on top of the strict URL syntax, I am not 100% sure how they do it, but it probably involves a lot of heuristics and trial and error. The parser of ZnUrl is just 3 to 4 methods. There is nothing preventing somebody from making a new ZnLoseUrlParser, but it won't be easy. > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

March 24, 2019

FFI to UFFI

by TomaÅ¾ Turk

Pierce, Esteban, many thanks for your most valuable directions. Live and learn :-) Tomaz ------ Original Message ------ From: "Esteban Lorenzano" <estebanlm(a)gmail.com> To: "TomaÅ¾ Turk" <tomaz.turk(a)ef.uni-lj.si>; "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Sent: 24.3.2019 8:10:32 Subject: Re: [Pharo-users] FFI to UFFI >One final consideration: > >Truth is, once you load it in P7, the package should work (at least in >32 bits, I do not think is made thinking on 64bits platforms). Both >notations ends calling same primitives. > >This means, if your intentions are just to play a bit and see how >things work: you should not need to do the translation >:) > >Esteban > >Ps: I just tried in P8 the approach to load I proposed. It throws an >error but loads. > > > >>On 23 Mar 2019, at 18:22, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: >> >>I started to play with ODBC package upgrade from Pharo 4.0 to 7.0 >>(http://smalltalkhub.com/mc/PharoExtras/ODBC) more or less as an >>exercise. As a smalltalk novice I stubmled to the challenge of, as it >>seems, an old FFI syntax. When I try to load the package into Pharo >>7.02 on Windows, I get this error: >> >><br0g15dj.png> >> >>I have two questions: >>- Is there any elegant way to successfuly load the package into Pharo >>7 to get started with the code adaptation? >>- And, of course, I'd be grateful if someone could point me into the >>right direction of how to tackle with the above cdecl syntax with the >>new UFFI. >> >>Best wishes >>Tomaz >

March 24, 2019

Re: [Pharo-users] FFI to UFFI

by Esteban Lorenzano

One final consideration: Truth is, once you load it in P7, the package should work (at least in 32 bits, I do not think is made thinking on 64bits platforms). Both notations ends calling same primitives. This means, if your intentions are just to play a bit and see how things work: you should not need to do the translation :) Esteban Ps: I just tried in P8 the approach to load I proposed. It throws an error but loads. > On 23 Mar 2019, at 18:22, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > > I started to play with ODBC package upgrade from Pharo 4.0 to 7.0 (http://smalltalkhub.com/mc/PharoExtras/ODBC <http://smalltalkhub.com/mc/PharoExtras/ODBC>), more or less as an exercise. As a smalltalk novice I stubmled to the challenge of, as it seems, an old FFI syntax. When I try to load the package into Pharo 7.02 on Windows, I get this error: > > <br0g15dj.png> > > I have two questions: > - Is there any elegant way to successfuly load the package into Pharo 7 to get started with the code adaptation? > - And, of course, I'd be grateful if someone could point me into the right direction of how to tackle with the above cdecl syntax with the new UFFI. > > Best wishes > Tomaz

March 24, 2019

Re: [Pharo-users] FFI to UFFI

by Esteban Lorenzano

Now, about translation to UFFI, is not so simple, but not so complex (it just needs some work). 1) you need to declare the types like SQLRETURN, usually in a shared pool, something like: SQLRETURN := #uint. That you later will include in your ODBC classes. 2) you need to translate structures (this is the hardest part). In UFFI, you declare structures extending FFIExternalStructure and declaring fields with something like this: fieldsDesc "self rebuildFieldAccessors" ^ #( double ascent; double descent; double height; double max_x_advance; double max_y_advance; ) Finally, you need to translate the function calls. The function you are putting as an example would be translated like that: sqAllocEnv: environmentHandle ^ self ffiCall: #(SQLRETURN SQAllocEnv(SQLHENV environmentHandle) ) Which, if you see, is a direct translation of the function call :) Esteban PS: I have in my infinite TODO list to do thisâ¦ but I do not had the time yet :( Also, the real problem is that once you are working with UFFI, the design possibilities of a library change a lot, and you can do something a lot more close to real OOP. Thatâs what happened to me when I fist took a look to the package to translate itâ¦ I said âOh boy, I would do this very differently" :P > On 23 Mar 2019, at 18:22, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > > I started to play with ODBC package upgrade from Pharo 4.0 to 7.0 (http://smalltalkhub.com/mc/PharoExtras/ODBC <http://smalltalkhub.com/mc/PharoExtras/ODBC>), more or less as an exercise. As a smalltalk novice I stubmled to the challenge of, as it seems, an old FFI syntax. When I try to load the package into Pharo 7.02 on Windows, I get this error: > > <br0g15dj.png> > > I have two questions: > - Is there any elegant way to successfuly load the package into Pharo 7 to get started with the code adaptation? > - And, of course, I'd be grateful if someone could point me into the right direction of how to tackle with the above cdecl syntax with the new UFFI. > > Best wishes > Tomaz

March 24, 2019

Re: [Pharo-users] FFI to UFFI

by Esteban Lorenzano

Hi, One way: 1) load the old compiler from here: https://github.com/pharo-project/OldCompiler <https://github.com/pharo-project/OldCompiler> 2) Activate it: SmalltalkImage compilerClass: Compiler. 3) load ODBC 4) restore OpalCompiler SmalltalkImage compilerClass: OpalCompiler. This *should* work. Esteban > On 23 Mar 2019, at 18:22, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > > I started to play with ODBC package upgrade from Pharo 4.0 to 7.0 (http://smalltalkhub.com/mc/PharoExtras/ODBC <http://smalltalkhub.com/mc/PharoExtras/ODBC>), more or less as an exercise. As a smalltalk novice I stubmled to the challenge of, as it seems, an old FFI syntax. When I try to load the package into Pharo 7.02 on Windows, I get this error: > > <br0g15dj.png> > > I have two questions: > - Is there any elegant way to successfuly load the package into Pharo 7 to get started with the code adaptation? > - And, of course, I'd be grateful if someone could point me into the right direction of how to tackle with the above cdecl syntax with the new UFFI. > > Best wishes > Tomaz

March 24, 2019