December 2017 - Pharo-users

Re: [Pharo-users] Breakpoints in Pharo

by jtuchel＠objektfabrik.de

Ben, I don't think you can compare #halt with Breakpoints. Breakpoints have two main advantages over halts: * They do not change source code, so there is no diff between a method version with and without this debugging aid. Helps a lot, especially in times when you urgenztly need to fix a bug in production code. There's no time to read diffs that baiscally have zero meaning saturday nights at 2:00 AM... * They cannot easily be packaged into the production/runtime image, because they are not part of the source code. Thus it cannot be "forgotten" when you deploy. This is not relevant in Pharo, where there is no packaging step as in VW or VAST, but there it really is. A halt in production code makes for a great monday morning when the new version was just shipped ;-) So when you work on code to actually ship into users' hands, there are quite some good arguments for Breakpoints. There's more to them, like conditional Breakpoints that make debugging a bug so much easier and Watchpoints, but these would make my message way too long. Of course all of the above-mentioned things can be achieved using appropriate handlers for #halt and add stuff to them or make #halts just ignored at deployment time, but these are also steps that can be forgotten... Joachim Am 27.12.17 um 00:26 schrieb Ben Coman: > Hi Andrei, > > On 26 December 2017 at 09:51, Andrei Stebakov <lispercat(a)gmail.com > <mailto:lispercat@gmail.com>> wrote: > > Can I expect that break points in Pharo work in the same way as in > Visual Works? > When I set a break point in Pharo (6.1 on Windows), it displays a > red dot with an exclamation mark and when I send this message to > an object, the debugger doesn't get invoked. > > > Sorry I'm not familiar with VisualWorks. > If I define this method (Pharo 6.1 on Linux)... > Â Â Object >> myTest > Â Â Â Â "Object new myTest" > Â Â Â Â self halt. > Â Â Â Â self inform: 'test'. > > then evaluate the comment, a debugger is invoked. > > If your example is different, could you explain it in more detail? > > cheers -ben -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1Â Â Â Â Â Â Â Â Â Â Â Â Â http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0Â Â Â Â Â Fax: +49 7141 56 10 86 1

Dec. 27, 2017

Pharo Catalog Submission

by Evan Donahue

Hi, I have just finished making a BaselineOf and ConfigurationOf for submitting my github-based project to the Pharo catalog. If my ConfigurationOf is with my code on github (via Iceberg), what Metacello command should I run to test that it works correctly before submitting to the catalog (to fetch the ConfigurationOf and then load it)? Thanks, Evan

Dec. 27, 2017

Re: [Pharo-users] Iceberg regex

by Holger Freyther

> On 26. Dec 2017, at 23:02, Ian Ian <icjohnsoia(a)gmail.com> wrote: Hey! > Yes. That is how it is on github but there are private hit serveers. My own, for example. > > I found it usable after I changed the regex in both classes where it exists. I tried to replace some of regexps with ZnUrl but some of the ssh/scp/git urls are not valid URIs and then tweaked it to include the port number. Maybe someone else has another pass it? In PR#473[1] I mentioned git:git@domin.com:path as a non valid URL that is happily accepted by git itself. :} holger [1] https://github.com/pharo-vcs/iceberg/pull/473

Dec. 27, 2017

Re: [Pharo-users] Breakpoints in Pharo

by Ben Coman

Hi Andrei, On 26 December 2017 at 09:51, Andrei Stebakov <lispercat(a)gmail.com> wrote: > Can I expect that break points in Pharo work in the same way as in Visual > Works? > When I set a break point in Pharo (6.1 on Windows), it displays a red dot > with an exclamation mark and when I send this message to an object, the > debugger doesn't get invoked. > Sorry I'm not familiar with VisualWorks. If I define this method (Pharo 6.1 on Linux)... Object >> myTest "Object new myTest" self halt. self inform: 'test'. then evaluate the comment, a debugger is invoked. If your example is different, could you explain it in more detail? cheers -ben

Dec. 26, 2017

Re: [Pharo-users] pharo 64 bits on mac os X - El Capitan

by Manuel Leuenberger

I ran Pharo 6 64 bit on El Capitan some time ago. I am not sure about the exact version of Pharo and VM though. Have you tried with older VMs? Cheers, Manuel > On 26 Dec 2017, at 17:22, Renaud de Villemeur <renaud.devillemeur(a)gmail.com> wrote: > > Hi all > > I want to run pharo on Mac Os X. It is on old hardware, and thus, I cannot upgrade to latest version of MacOsX. I am trying to run in on El Capitan - v 10.11.6. > > When I start pharo from the command line, I have this error: > $ ./Pharo > > Illegal instruction Tue Dec 26 11:12:55 2017 > > > VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ Date: Thu Jul 20 12:42:21 2017 -0700 $ > Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ > > Abort trap: 6 > > I am using latest 6.1 64bit link from pharo web site. > > If I am using the command line install with curl, I have the following result: > ./pharo-ui > > Illegal instruction Tue Dec 26 11:19:49 2017 > > > VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ Date: Thu Jul 20 12:42:21 2017 -0700 $ > Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ > > ./pharo-ui: line 11: 991 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" "$@" > > Any hint ? Or should we specify a minimal version of mac os X for 64 bit version ? > > Thanks in advance for your help > Renaud >

Dec. 26, 2017

Re: [Pharo-users] Object Persistence

by Manuel Leuenberger

Iâve always liked Neo4j to persist object graphs. Also has a nice query language. The database is not fool-proof (isolation issues, out of memory on expensive queries), but works fine for analytics. > On 25 Dec 2017, at 10:43, Ian Ian <icjohnsoia(a)gmail.com> wrote: > > Hi All, > > Thoughts of a purely OO nature? > > :)

Dec. 26, 2017

Re: [Pharo-users] Object Persistence

by Offray Vladimir Luna CÃ¡rdenas

But if VOSS is GPL, that doesn't imply that, when ported, all Pharo could become GPL, as discussed time and again in the list? Cheers, Offray On 25/12/17 10:01, Stephane Ducasse wrote: > the author of omnibase told me that he always wanted to port it to > Pharo. But may be someone should do it. > There is also VOSS that is open source even if GPL that could be > ported to pharo but this is an effort too. > > Stef > > On Mon, Dec 25, 2017 at 10:43 AM, Ian Ian <icjohnsoia(a)gmail.com> wrote: >> Hi All, >> >> Thoughts of a purely OO nature? >> >> :) >

Dec. 26, 2017

Re: [Pharo-users] How to connect to DB2

by Andrei Stebakov

Thank you for the answers! I thought ODBC was deprecated from Garage, I'll give it another look. On Fri, Dec 22, 2017 at 10:53 PM, Thomas Sattler <tomsattler(a)gmail.com> wrote: > I have no problem using Garage to connect to Postgres. Don't know if it > will work with DB2, but since it's ODBC, it should. > > On Fri, Dec 22, 2017 at 6:36 PM, Andrei Stebakov <lispercat(a)gmail.com> > wrote: > >> Hi Stef >> >> I already checked Garage, it doesn't have support for DB2. It used to >> have support for odbc, but now it's deprecated. >> >> Andrei >> >> On Dec 22, 2017 15:11, "Stephane Ducasse" <stepharo.self(a)gmail.com> >> wrote: >> >>> Hi andrei >>> >>> I do not know the status of OBDC but you should know that code on >>> squeaksource is in general quite old. >>> Have a look at Garage which is a kind of JBDC. >>> >>> https://github.com/pharo-rdbms/garage >>> >>> You should probably have a version available via the catalog >>> >>> Stef >>> >>> On Fri, Dec 22, 2017 at 2:43 PM, Andrei Stebakov <lispercat(a)gmail.com> >>> wrote: >>> > Hi Stef >>> > >>> > Gofer new >>> > squeaksource: 'ODBC'; >>> > package: 'ConfigurationOfODBC'; load. >>> > (Smalltalk at: #ConfigurationOfODBC) load. >>> > >>> > When I execute the code above I got an exception doesNotUnderstand: >>> > #selector in RBParser>>externalFunctionDeclaration. Looks like >>> currentScope >>> > variable is not defined. >>> > Also if I install ODBC from the catalog it also fails. >>> > >>> > Andrei >>> > >>> > >>> > On Fri, Dec 22, 2017 at 2:19 AM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> >>> > wrote: >>> >> >>> >> Hi andrei >>> >> >>> >> First welcome to this list. >>> >> Second can you explain to us what is the experience that you did so >>> >> that you can state that ODBC is broken in Pharo 6.1? >>> >> >>> >> Stef >>> >> >>> >> On Thu, Dec 21, 2017 at 11:48 PM, Andrei Stebakov < >>> lispercat(a)gmail.com> >>> >> wrote: >>> >> > Looks like ODBC is broken in Pharo 6.1. >>> >> > What's the best way to get access to DB2 in Pharo? >>> >> > >>> >> > >>> >> >>> > >>> >>> >

Dec. 26, 2017

pharo 64 bits on mac os X - El Capitan

by Renaud de Villemeur

Hi all I want to run pharo on Mac Os X. It is on old hardware, and thus, I cannot upgrade to latest version of MacOsX. I am trying to run in on El Capitan - v 10.11.6. When I start pharo from the command line, I have this error: $ ./Pharo Illegal instruction Tue Dec 26 11:12:55 2017 VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Abort trap: 6 I am using latest 6.1 64bit link from pharo web site. If I am using the command line install with curl, I have the following result: ./pharo-ui Illegal instruction Tue Dec 26 11:19:49 2017 VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ ./pharo-ui: line 11: 991 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" "$@" Any hint ? Or should we specify a minimal version of mac os X for 64 bit version ? Thanks in advance for your help Renaud

Dec. 26, 2017

Re: [Pharo-users] Athens error

by Pavel Krivanek

2017-12-26 14:32 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Running your drgeo.image on a recent linux pharo 64 bit vm gives this > error message first: > > /home/nicolai/devel/pharo/Pharo7.0-32bit-52a28a8.sources. > > With pharo 7, every (bootstrapped)image needs its own sources file? > Every Pharo 7 build creates own sources file but this sources file can be shared between several images based on this build. So for final Pharo 7 we may release one sources file but I doubt that we will do it. During bootstrap all code is loaded into the image as new code so at the end you have empty sources file and huge changes file. We condense such changes file and transform it into sources file so you have empty changes. But we would like have sources directly in the image in compressed form. -- Pavel > > > 2017-12-26 11:59 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: > >> Just make a drgeo build with latest image as of today, the problem is the >> same with latest image, as long as the source file is not present. Here is >> the newest built[1] >> >> Hilaire >> >> >> [1] https://www.dropbox.com/s/wc18e21p371z28f/DrGeo.app-18.01a.zip?dl=0 >> >> Le 26/12/2017 Ã 11:15, Pavel Krivanek a Ã©crit : >> >>> Hi Hilaire >>> >>> your P7 image is older and has problems with FreeType fonts >>> initialization that should be fixed in the newest builds. Maybe that is >>> cause of the Athens issues you are facing. Please upgrade. >>> >>> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> >> >

Dec. 26, 2017