- Pharo-users - lists.pharo.org

Re: [Pharo-users] what is wrong here. Tests are green but the outcome with real code is much to high

by Richard O'Keefe

Not an answer to your specific question, but your #move... methods look very odd. I think you meant something like moveUpAFloor floor := floor + 1. moveDownAFloat floor := floor - 1. hasReachedBasement ^floor = -1 AH! Now I see it. You are reporting the LAST time that the lift reached the basement, but you were suppose to report the FIRST time. You want reachedBasement: input input withIndexDo: [:element :index | element = $( ifTrue: [self moveUpAFloor]. element = $) ifTrue: [self moveDownAFloor]. self hasReachedBasement ifTrue: [^index]]. "HERE" ^0 Or using a standard linear-search method, reachedBasement: input |floor| floor := 0. "ground" ^input findFirst: [:each | each = $( ifTrue: [floor := floor + 1]. "up" each = $) ifTrue: [floor := floor - 1]. "down" floor = -1 "basement"] On Tue, 18 Dec 2018 at 09:49, Roelof Wobben <r.wobben(a)home.nl> wrote: > hello > > I have this code > > hasReachedBasement: aFloor > "comment stating purpose of message" > > ^ aFloor = -1 > > initialize > "comment stating purpose of message" > > super initialize. > position := 1. > floor := 0 > > moveFloorDown: aFloor > "comment stating purpose of message" > > ^ floor := aFloor - 1 > > moveFloorUp: aFloor > "comment stating purpose of message" > > ^ floor := aFloor + 1 > > reachedBasement: input2 > input2 > withIndexDo: [ :element :index | > element = $( > ifTrue: [ self moveFloorUp: floor ] > ifFalse: [ self moveFloorDown: floor ]. > (self hasReachedBasement: floor) > ifTrue: [ position := index ] ]. > position ifNotNil: [ ^ position ] > > This works very fine with test input given by the challenge > but as soon as I do it with this : > https://gist.github.com/RoelofWobben/3be69976a6dd3531f01558b0ac563556 > > I see as answer : 6111 where I expect to see 1797 > > Anyone who can see what I did wrong ? > > Roelof > > >

Dec. 18, 2018

what is wrong here. Tests are green but the outcome with real code is much to high

by Roelof Wobben

hello I have this code hasReachedBasement: aFloor Â Â Â "comment stating purpose of message" Â Â Â ^ aFloor = -1 initialize Â Â Â "comment stating purpose of message" Â Â Â super initialize. Â Â Â position := 1. Â Â Â floor := 0 moveFloorDown: aFloor Â Â Â "comment stating purpose of message" Â Â Â ^ floor := aFloor - 1 moveFloorUp: aFloor Â Â Â "comment stating purpose of message" Â Â Â ^ floor := aFloor + 1 reachedBasement: input2 Â Â Â input2 Â Â Â Â Â Â withIndexDo: [ :element :index | Â Â Â Â Â Â Â Â Â element = $( Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ self moveFloorUp: floor ] Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ self moveFloorDown: floor ]. Â Â Â Â Â Â Â Â Â (self hasReachedBasement: floor) Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ position := index ] ]. Â Â Â position ifNotNil: [ ^ position ] This works very fine with test input given by the challenge but as soon as I do it with this : https://gist.github.com/RoelofWobben/3be69976a6dd3531f01558b0ac563556 I see as answer : 6111 where I expect to see 1797 Anyone who can see what I did wrong ? Roelof

Dec. 17, 2018

Re: [Pharo-users] NeoCSV

by Sven Van Caekenberghe

Loading a Tonel project on GitHub using a BaselineOf only works in Pharo 6.1 and higher, AFAIU. Pharo 5 is already pretty old ... > On 17 Dec 2018, at 19:09, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: > > Thanks, Sven! I'm trying to load NeoCSV in Pharo 5.0 from GitHub, but I get > > Could not resolve: BaselineOfNeoCSV [BaselineOfNeoCSV] in C:\users â¦ > > However, it loaded nicely in Pharo 6.1 32-bit. Both are on the same location > (branch) on the disk. > > Is there any suggestion what to do (how to debug the situation) if one gets > this kind of messages? Another misterious one is "there was an error â¦ > process was cancelled" or similar, when loading with Project Catalog. > > Pharo is a great tool and I decided to learn it and possibly contribute, > however making a stable image with the necessary tools can get quite time > consuming. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 17, 2018

Re: [Pharo-users] NeoCSV

by eftomi

Thanks, Sven! I'm trying to load NeoCSV in Pharo 5.0 from GitHub, but I get Could not resolve: BaselineOfNeoCSV [BaselineOfNeoCSV] in C:\users â¦ However, it loaded nicely in Pharo 6.1 32-bit. Both are on the same location (branch) on the disk. Is there any suggestion what to do (how to debug the situation) if one gets this kind of messages? Another misterious one is "there was an error â¦ process was cancelled" or similar, when loading with Project Catalog. Pharo is a great tool and I decided to learn it and possibly contribute, however making a stable image with the necessary tools can get quite time consuming. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 17, 2018

Re: [Pharo-users] voygae on P7 install problens on Windows

by Roelof Wobben

Dec. 17, 2018

http://planet.smalltalk.org ?

by Sven Van Caekenberghe

Anybody knows what happened to http://planet.smalltalk.org ? I find it quite handy to catch up with multiple blog posts / feeds.

Dec. 17, 2018

Re: [Pharo-users] voygae on P7 install problens on Windows

by Sanjay Minni

Hi Roelof, can you check if your problem has any bearing to this thread just discussed http://forum.world.st/Voyage-td5088984i20.html --- Sanjay Minni +91-9900-902902 On Mon, 17 Dec 2018 at 03:26, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, 17 Dec 2018 at 03:25, Roelof Wobben <r.wobben(a)home.nl> wrote: > >> Hello >> >> Are there more people who cannot install voyage on Windows >> I see a message that the name is too long >> > > Could you clarify this last statement... > > >> where pharo works on the root >> > > Did you mean you are already running pharo from somewhere like "C:\pharo" ? > ...which was the first thing I would suggest trying? > > cheers -ben >

Dec. 17, 2018

Re: [Pharo-users] Some issues with Pharo and Ubuntu

by Sven Van Caekenberghe

To load the latest Seaside in Pharo 7 I use the develop branch: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:develop/repository'; load. > On 17 Dec 2018, at 16:36, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Hello, > > I am trying Pharo with Docker and I will leave here some issues I had since I am unsure where I should report them. The command I am running is: > > Metacello new baseline: 'Employees'; > repository: 'tonel:///home/employeesSource/pharo/'; > ignoreImage; > onConflict: [ :ex | ex useIncoming ]; > onWarning: [ :ex | Transcript crShow: ex ]; > silently; > load: #(core). > > > Ubuntu 16.04, Pharo 61 64bits -> Ok > > Ubuntu 16.04, Pharo 70 64bits -> Fail > > Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] > --- cache > Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- > https://github.com/SeasideSt/Seaside.git[v3.2.5] > --- cache > Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- > https://github.com/SeasideSt/Seaside.git[v3.2.5] > --- cache > Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. > > > Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> Fail > > Seems like libgit is not found and it try to use one internal, but the link is broken. > > Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo > Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo > Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): > libcurl-gnutls.so.4: cannot open shared object file: No such file or directory > ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): > libcurl-gnutls.so.4: cannot open shared object file: No such file or directory > tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/ > libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/ > ) Not a directory > [31mError: External module not found > [0mExternalLibraryFunction(Object)>>error: > ExternalLibraryFunction(Object)>>externalCallFailed > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > LGitLibrary>>libgit2_init > FFICalloutAPI>>function:module: > LGitLibrary(Object)>>ffiCall: > LGitLibrary>>libgit2_init > LGitLibrary>>initializeLibGit2 > LGitGlobal class>>checkInitialized > > > > Regards, > Vitor

Dec. 17, 2018

Some issues with Pharo and Ubuntu

by Vitor Medina Cruz

Hello, I am trying Pharo with Docker and I will leave here some issues I had since I am unsure where I should report them. The command I am running is: Metacello new baseline: 'Employees'; repository: 'tonel:///home/employeesSource/pharo/'; ignoreImage; onConflict: [ :ex | ex useIncoming ]; onWarning: [ :ex | Transcript crShow: ex ]; silently; load: #(core). Ubuntu 16.04, Pharo 61 64bits -> *Ok* Ubuntu 16.04, Pharo 70 64bits -> *Fail* Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> *Fail* Seems like libgit is not found and it try to use one internal, but the link is broken. Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): libcurl-gnutls.so.4: cannot open shared object file: No such file or directory ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): libcurl-gnutls.so.4: cannot open shared object file: No such file or directory tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/) Not a directory [31mError: External module not found [0mExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: LGitLibrary>>libgit2_init FFICalloutAPI>>function:module: LGitLibrary(Object)>>ffiCall: LGitLibrary>>libgit2_init LGitLibrary>>initializeLibGit2 LGitGlobal class>>checkInitialized Regards, Vitor

Dec. 17, 2018

Re: [Pharo-users] GlorpSQLite not finding sqlite library on Mac

by Pierce Ng

On Sun, Dec 16, 2018 at 10:25:11AM -0800, Todd Blanchard via Pharo-users wrote: > Metacello new > repository: 'github://pharo-rdbms/glorp-sqlite3'; > baseline: 'GlorpSQLite'; > load. Hi Todd, Pharo 6 or 7? 32- or 64-bit? > This seems to be the only way to get SQLite support? There is no > standalone UFFI library? Not that I have a problem with it, I know > and like GLORP. GlorpSQLite is built on the standalone SQLite UFFI library. > Then I ran the basic UDBCSQLite tests and they all fail with 'External > module not found'. I presume this means that the sqlite library was > not found but the best I can find is a method #library that returns > #sqlite > Reading the well written > https://files.pharo.org/books-pdfs/booklet-uFFI/UFFIDRAFT.pdf I gather > that I should subclass FFILibrary to make a SQLiteLibrary and have > UDBCSQLite class that implements #macModuleName to return > '/usr/local/Cellar/libspatialite/4.3.0a_6/libspatialite.dylib'? The library was written before that convention was established. Currently it is UDBCSQLite3Library (subclassing Object) and its #library says this: library Smalltalk os isMacOS ifTrue: [ ^ #sqlite3 ]. ^ 'sqlite3' This worked before as I had used it with Pharo 5 when my Mac was on El Capitan and Sierra. The Mac is now on High Sierra. Testing... Ok, the system-supplied library is named libsqlite3.0.dylib. After some experimentation, copying/renaming said library works: % cp -p /usr/lib/libsqlite3.0.dylib % ~/Pharo.app/Contents/MacOS/Plugins/libsqlite3.dylib Now 64-bit Pharo 60543 finds the dylib, the SQLite tests run and pass. I also tested keeping the '3.0' in the dylib file name, modifying the #library method accordingly, and evaluating 'UDBCSQLite3Library reset' to clear the singleton class variable. I've not run into this situation before because I've always used my own custom SQLite shared library that includes JSON, FTS etc extensions. For good measure I also ran the Glorp tests and got 891 run, 890 passes, 1 error. The error is due to my changing SQLite's boolean handling, see https://www.samadhiweb.com/blog/2018.05.20.sqlite.boolean.html The test error has been fixed for Pharo 7. Not yet back-ported for Pharo 6. To load GlorpSQLite for Pharo 7, use the Catalog Browser, or, equivalently, load from my repo: Metacello new repository: 'github://PierceNg/glorp-sqlite3:pharo7'; baseline: 'GlorpSQLite'; load. > spatialite Cool! Please let me know how this goes. Back in Pharo 4's Native Boost days, NBSQLite as it was called then supported both SQLite and SQLcipher. I had experimented with loading libsqlcipher3 from UDBCSQLcipher3Library, which subclasses UDBCSQLite3Library, and IIRC also via some class variable in UDBCSQLite3Library determining which shared library to load. Torsten Bergmann kindly ported NBSQLite to UFFI. The SQLcipher part is still on my to-do list, and I am also interested to have (Glorp|UDBC)SQLite load Spatialite (and maybe even libspatialitecipher) cleanly. Pierce

Dec. 17, 2018