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

Why version `GLIBC_2.15'?
by Bernardo Ezequiel Contreras Oct. 3, 2014

Oct. 3, 2014

hi all, i just want to know why the pharo-vm is compiled with `GLIBC_2.15'? is there a bug due to glibc's version? thanks. -- Bernardo E.C. Sent from a cheap desktop computer in South America.

2 2

Catch Response 500 error in ZnClient
by Nicolai Hess Oct. 3, 2014

Oct. 3, 2014

How to catch a ZnResponse(500 Internal Server Error) ? (see fogbugz issue 13905) I tried to add a ifFail:[....] block but it does not get called on this response. Nicolai

2 3

blogging about Pharo stuff? send me your link!
by Esteban Lorenzano Oct. 3, 2014

Oct. 3, 2014

I know, there are several concentrator pages like http://planet.smalltalk.org, etc. but I want to put your blog here: http://pharo.org/blogs So, please send me (in private, to not pollute this list) your Pharo related blog :) Esteban

5 8

RB Tests failing
by Yuriy Tymchuk Oct. 2, 2014

Oct. 2, 2014

Hi, now when you download a new Pharo4 image there are 3 tests failing/erroring: Failures: RBRenameInstanceVariableTest>>#testRenameInstVarAccessorsReferences Errors: RBRemoveClassTest>>#testRemoveClass RBExtractMethodTest>>#testExtractMethodThatMovesTemporaryVariable Is there an issue about that? Is anybody looking into it? Uko

4 3

GTInspector + Fuel
by Yuriy Tymchuk Oct. 1, 2014

Oct. 1, 2014

Hi, sorry if this is a known thing, but Iâve just notices this and it made my day. So in GTInspector you can browse filesystem, but when you select a fuel file, you can press a "plusâ button in top right corner, and it materialises the object. Amazing. Uko

4 5

GTTool bug:
by stepharo Oct. 1, 2014

Oct. 1, 2014

edit: aText label: labelString accept: anAction "Open an editor on the given string/text" ^(Smalltalk tools workspace openLabel: labelString) acceptContents: aText; acceptAction: anAction; yourself. -> DNU UIManager default edit: 'jlklkjk' label: 'lkjlkjjkl'

5 9

GTTools bug - why I cannot select the text by simply clicking at the end of it....
by stepharo Oct. 1, 2014

Oct. 1, 2014

With the previous tools I can select a piece of text by clicking after its last element and now I cannot or I can but sometimes. So what is the fix? Stef

5 15

GTools (GTPlayground and GTInspector) integrated
by Esteban Lorenzano Oct. 1, 2014

Oct. 1, 2014

â¦ that :) Which means that now we have a long way to polish them until Pharo4 release. Please test and provide feedback :) Esteban

8 29

Re: [Pharo-dev] [Vm-dev] [squeak-dev] Maintainer of FFI-Package
by Eliot Miranda Sept. 30, 2014

Sept. 30, 2014

Hi Annick, On Mon, Sep 29, 2014 at 5:30 AM, Annick Fron <list(a)afceurope.com> wrote: > Hi, > > > I have recently made some experiments with pharo and FFI, and I have ran > into problems with callbacks. > I am using linux 32 bits. > First question : when calling a dynamic library is it necessary that it > exports all symbols ? What if symbols are noted Â« U Â» (undefined) ? > If you have undefined symbols in an external library, they need to be resoled by the VM or other libraries loaded in the system. If any are not resolved the library will fail to load. > 2) On one of my callbacks got the message Â« callback failed to own the VM > Â» . Have you any idea of where it comes from ? > Yes. This means you're trying to callback from a different thread than the VM thread. hat isn't supported yet. > 3) If the callback is called in a different thread, is it a problem ? > Yes. 4) On Pharo I have an error on the following : is it incorrect ? It is a 64 > bits problem ? > Using FFI Linux examples. > > testGetOurWindowLocation > "self new testGetOurWindowLocation" > > | display ourWindow aParent anX anY aWidth aHeight aBorderWidth aDepth | > display := X11Display XOpenDisplay: nil. > ourWindow := display ourWindow. > (Alien lookup: 'XGetGeometry' inLibrary: 'X11') > primFFICallResult: nil > withArguments: > {display. > ourWindow. > (aParent := Alien new: 4). > (anX := Alien new: 4). > (anY := Alien new: 4). > (aWidth := Alien new: 4). > (aHeight := Alien new: 4). > (aBorderWidth := Alien new: 4). > (aDepth := Alien new: 4)}. > (anX unsignedLongAt: 1) inspect > What's the error you get? Annick > Le 28 sept. 2014 Ã 21:44, David T. Lewis <lewis(a)mail.msen.com> a Ã©crit : > > > On Sun, Sep 28, 2014 at 09:04:59AM -0400, David T. Lewis wrote: > >> > >> On Sun, Sep 28, 2014 at 11:19:30AM +0200, Nicolai Hess wrote: > >>> Who is the maintainer of the FFI-Package for > >>> Squeak and/or Pharo ? > >>> I especially interested in the FFI-Unix examples > >>> and the state on working FFI on linux for current squeak release > >>> (AFAIK it does not work with "squeak all in one" 4.5) > >>> > >> > >> The FFI package, including the FFI-Unix examples that you mention, is at > >> http://source.squeak.org/FFI. > >> > >> The primary author was Andreas Raab. Eliot Miranda is the most recent > >> contributor, and he is probably the most knowledgeable in this area. > >> Currently, the Squeak core developers (those with commit rights to > Squeak > >> trunk) have commit rights to the FFI project, and can make updates as > needed. > >> > >> The FFI examples for Unix work with the old FFI plugin, which is still > >> present in the interpreter VM. The active development of Squeak FFI is > >> taking place in Cog, and I'm not sure if the old FFI examples work with > >> the newer plugins (which would be present in the Squeak all-in-one). > >> The FFI plugin in the interpreter VM (i.e. trunk VMMaker) needs to be > >> updated, and presumably the FFI examples may need some updates as well. > > > > A small but important correction: For the old plugin (currently in the > > interpreter VM), FFI works only for a 32-bit VM. It also works for a > 64-bit > > VM, but only if the patches in http://bugs.squeak.org/view.php?id=7237 > have > > been applied (in other words, if you compiled it yourself and included > > those patches). > > > > This is mainly of historical interest, although it is possible that some > > of the 64-bit patches will prove helpful for the newer FFI plugin. But > > the emphasis now should be on Eliot's more recent FFI work. > > > > Dave > > > > > > > -- best, Eliot

1 0

Context representation in current VM
by Martin McClure Sept. 30, 2014

Sept. 30, 2014

I'm updating the exceptions chapter of Deep Into Pharo, which currently contains this text: "...some Smalltalk implementations use the native C execution stack of the virtual machine to avoid creating objects all the time. The current Pharo virtual machine does actually use full Smalltalk objects all the time; for speed, it recycles old method context objects rather than creating a new one for each message-send." Is this still true as of Pharo 4? I'd gotten the idea that this hadn't been true for a while, that the Cog VMs that Pharo is using did use a non-object stack to cache the top N contexts, only converting to actual Context objects when necessary. Thanks, -Martin

4 5