- Pharo-dev - lists.pharo.org

Re: [Pharo-project] MethodWrappers

by Marcus Denker

On Apr 20, 2012, at 7:30 PM, Paul DeBruicker wrote: > If you were to integrate MethodWrappers into Pharo today would you still use > these packages: > > Compiler-eem.214 & Compiler-eem.215, > Kernel-619 to Kernel-eem.623 > I integrated all the changes of eliot that he did for MethodWrappers. But why not use the MethodWrappers that use run:with:in:? (the package that was loaded in 1.3 Full)? > or use the latest from Squeak trunk? No chance. The systems are too different by now. -- Marcus Denker -- http://marcusdenker.de

April 20, 2012

Re: [Pharo-project] Unresponsive 1.4 image

by Camillo Bruni

Hi Janko, Can you tell on which OS? best cami On 2012-04-20, at 19:04, Janko MivÅ¡ek wrote: > Hi guys, > > Well, this bug is something you should finally find and solve ASAP, > because it certainly don't give a confidence to the Pharo for serious work. > > So, I just have again an image unresponsive to keyboard and mouse input. > Built from latest 1.4 OneClick. If someone wants it for debugging, I'm > happy to send you the whole image. > > Image became unresponsive after I started it again. Image was otherwise > snapshoted in background every hour. Is this maybe a reason? > > Best regards > Janko > > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

April 20, 2012

Re: [Pharo-project] Unresponsive 1.4 image

by phil＠highoctane.be

I have been experiencing such freezes as well. Example: with a textmorph being resized through a corner down the bottom of the screen, there is a freeze. Also with full screen I had a lock with a 1.3 I have no clue on how to diagnose. If there are pointers, I am ready to search. I was thinking of running a VM under the debugger to check where things were going south . It happens to be with a StackVM or a CogVM or a NBCogVM. No crash but a freeze. Is there a way to instrument the loading process so that we can track what's failing? I second you on the 'trustable' platform bit. Phil 2012/4/20 Janko MivÅ¡ek <janko.mivsek(a)eranova.si> > Hi guys, > > Well, this bug is something you should finally find and solve ASAP, > because it certainly don't give a confidence to the Pharo for serious work. > > So, I just have again an image unresponsive to keyboard and mouse input. > Built from latest 1.4 OneClick. If someone wants it for debugging, I'm > happy to send you the whole image. > > Image became unresponsive after I started it again. Image was otherwise > snapshoted in background every hour. Is this maybe a reason? > > Best regards > Janko > > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 20, 2012

Re: [Pharo-project] MethodWrappers

by Paul DeBruicker

If you were to integrate MethodWrappers into Pharo today would you still use these packages: Compiler-eem.214 & Compiler-eem.215, Kernel-619 to Kernel-eem.623 or use the latest from Squeak trunk? I'm also trying to build a DTrace enabled unix VM based on Adrian Lienhards work here: http://www.adrian-lienhard.ch/blog?dialog=smalltak-meets-dtrace. Has anyone already made one for linux that I could just use? Thanks Eliot Miranda-2 wrote > > On Wed, Sep 21, 2011 at 3:48 AM, Torsten Bergmann <astares@> wrote: > >> Hi Eliot, >> >> at [1] you mentioned a port of MethodWrappers to Squeak 4.2. >> Is there also a port for Pharo available or do you plan to >> port it? >> > > I was hoping someone with focus on Pharo would integrate the necessary > compiler and kernel changes into Pharo. The Squeak trunk packages are > Compiler-eem.214 & Compiler-eem.215, and Kernel-619 to Kernel-eem.623. > I've > attached the diffs. Notionally file in Compiler-213-214.st & > Kernel-618-619.st, then file-in Compiler-214-215.st & Kernel-619-623.st. > These are generally useful, a) restoring the ability to create subclasses > of CompiledMethod, and b) fixing various subtle copying-related > state-sharing bugs with AdditionalMethodState (the objects that add > additional state to compiled methods, pragmas, properties and "extra inst > vars"). > > The MethodWrappers4.2 package should then just load. It serves as a model > for adding inst vars to CompiledMethod. > > >> For those who dont know about MethodWrappers: look at [2] >> > > Indeed. Yes, there's an alternative implementation above > objects-as-methods, but that implementation is far from complete. It > would > be good to see he same kind of completeness. e.g. with MethodWrappers you > can write > > | indent wrapper | > indent := 0. > wrapper := MwBlockMethodWrapper on: #benchFib inClass: Integer. > wrapper > beforeBlock: [:rcvr :args| > Transcript crtab: indent; print: rcvr; space; nextPutAll: #benchFib; > flush. > indent := indent + 1]; > afterBlock: [:rcvr :args| indent := indent - 1]. > [wrapper install. > 7 benchFib] ensure: [wrapper uninstall] > > whereas there are few if any examples with the objects-as-methods AFAICS. > >> >> Thanks >> Torsten >> >> >> [1] >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-September/16156… >> [2] http://www.refactory.com/Software/MethodWrappers/ >> -- >> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! >> Jetzt informieren: http://www.gmx.net/de/go/freephone >> > > > > -- > best, > Eliot > -- View this message in context: http://forum.world.st/MethodWrappers-tp3829576p4574768.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2012

Re: [Pharo-project] The video about Athens

by Sean P. DeNigris

I loaded into a fresh 1.4 image with: Gofer it squeaksource: 'Athens'; package: 'ConfigurationOfAthens'; load. (ConfigurationOfAthens project version: '1.0') load. When I doIt: m := AthensDemoMorph new openInWorld. I get Generic failure fnSpec: #(#bool #ioRegisterSurface #(#ulong #aCairoSurfaceHandle #, #void #* #sqSurfaceDispatchPtr #, #int #* #idHolder)) module: #SurfacePlugin errorCode: 1 -- View this message in context: http://forum.world.st/The-video-about-Athens-tp4571100p4574740.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2012

Re: [Pharo-project] [Pharo-users] Final 1.4 images...

by Sean P. DeNigris

Bernat Romagosa wrote > > I tried installing OmniBrowser but I couldn't manage to get autocomplete > working If you really need OB with completion, load with: (ConfigurationOfOmniBrowser project version: #stable) load: #('Dev'). -- View this message in context: http://forum.world.st/Final-1-4-images-tp4567574p4574719.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2012

Re: [Pharo-project] [NativeBoost] Generic failure errors when using nil for void* and char* arguments

by Schwab,Wilhelm K

Sig, For the record, you are not lazy. We'll start to live long and prosper when you get to it. Thanks! Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua(a)gmail.com] Sent: Friday, April 20, 2012 12:08 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [NativeBoost] Generic failure errors when using nil for void* and char* arguments On 20 April 2012 17:45, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > I wonder whether that should be on by default. I have had some real frustrations with FFI of late, and something like this might have avoided the problem. Unless it is easily discoverable, off is almost the same as non-existent. > Well, it depends on POV. For the strictness of usage, i thought it is better to pass explicitly (NBExternalAddress value: 0) than nil, so that your code passing correct value types to function(s). Automatic coercion and weak typing is something which i hate in C, and try to avoid (smalltalk is strong typed language) i.e. unsigned long a = 10000000; char x = a; producing only a compiler warning. and if you put: char x = (char) a; you can suppress it. But this is like placing a time bomb into your code, which you never know when it will explode. Weak typing is common source of many errors and bugs which is hard to find. This is one of the reasons, why i don't want nil to be a valid argument for functions expecting pointer(s) by default. Because while some library functions say that NULL is valid argument, on opposite side, there another functions which expecting a valid pointer value, and if you pass nil (as a result of not fully initialized object), you will crash the application. > Any rumblings on Spock? It would be nice to have even a facade that unifies the FFI/NB/Alien on all platforms. It would indelicate to mention that this was supposed to happen in January<g>. Yes, i am lazy guy, who cannot do much. Sorry :) The plans are still there: add callbacks support, add threading, unify Alien and NB. >I never really expected to see it that soon, given the problems I had going from 1.1.1 to 1.3 with FFI, and my rotating errors with Alien callbacks. I changed a bunch of FFI calls (in ways that I genuinely think should not have been necessary) and retreated to C functions for GSL callbacks. The latter is frustrating, BAD for my eventually being able to release a GSL binding (make that REALLY BAD), but not all bad because C++ is a better formula translator that Smalltalk, and the number crunching runs at native speeds. > > I think these things *can* work - they just don't at present, and the FFI/NB/Alien split makes it hard to know what to try. > i want that everything start working too.. so i can move on oh higher levels, since NativeBoost is infrastructural kind of project. > Bill -- Best regards, Igor Stasenko.

April 20, 2012

[Pharo-project] Unresponsive 1.4 image

by Janko MivÅ¡ek

Hi guys, Well, this bug is something you should finally find and solve ASAP, because it certainly don't give a confidence to the Pharo for serious work. So, I just have again an image unresponsive to keyboard and mouse input. Built from latest 1.4 OneClick. If someone wants it for debugging, I'm happy to send you the whole image. Image became unresponsive after I started it again. Image was otherwise snapshoted in background every hour. Is this maybe a reason? Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

April 20, 2012

Re: [Pharo-project] Athens/Cairo and Nautilus MNU: ClassTrait>>correspondingForTest

by Igor Stasenko

i have same strange behavior of nautilus.. On 20 April 2012 18:37, Alexis Parseghian <a.parseg(a)gmail.com> wrote: > After loading Athens from Metacello configuration, and following > Igor's advice as to where to fix the library path in TCairoLibrary > class. > > - Downloading a new official 1.4 image > - Loading ConfigurationOfAthens from squeaksource, version 1.0 > - viewing TCairoLibrary with the basic browser => ok on both instance > and class side > - load Nautilus from MetacelloConfigurationBrowser ("Load > configuration and stable version) > - viewing TCairoLibrary with Nautilus, instance side OK, class side > raises this MNU > - viewing TEasilyThemed (for instance) with Nautilus, works on both sides. > -- Best regards, Igor Stasenko.

April 20, 2012

Re: [Pharo-project] 1.4, seaside, comet, how to get it working

by Igor Stasenko

On 20 April 2012 18:41, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 20 Apr 2012, at 17:47, Igor Stasenko wrote: > >> Yes, you can look at my hacky implementation of Â SCouchDB, where i >> partially implemented >> the HTTP protocol and use streams for content. See >> http://www.squeaksource.com/SCouchDB >> >> there i use a stream to directly parse the input without waiting all >> data to arrive. >> This is also useful for up/downloading huge files, where content size >> can easily surpass the amount of RAM available. > > OK, I will have a look, but I don't think that will answer my questions. > > Zn already nicely handles streaming through its ZnStreamingEntity object: it captures all metadata and a reference to the stream and leaves it up to its user to drain it or to fill it. And indeed, that is the way to handle things like large uploads or downloads while not taking everything in memory at once. > Ah, so its already there.. less to worry about > Sven -- Best regards, Igor Stasenko.

April 20, 2012