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

[Pharo-project] NativeBoost opportunties?

by Schwab,Wilhelm K

Sig, Today, I ran into a bug of mine that I would not have had to track down if the various typed byte arrays (double in particular) existed. The more you can offer in that area, with indexing, bulk fill, bulk copy, etc., the better. I also ran into what appears to be a maximum number of arguments to an external call. Can you get around that? I can too, in this case. It's shameless, but I will "dumb down" the call so that FFI can handle it. There are arguments that I can default or provide from a shared library, and just call into a facade function exported from there. Shouldn't have to do that, clearly, but it will work. Bill

Sept. 26, 2010

Re: [Pharo-project] [Vm-dev] VM Maker: VMMaker-oscog.33.mcz

by Eliot Miranda

I would appreciate anyone interested in objects-as-methods on Cog pounding on the latest Cog VMs (http://www.mirandabanda.org/files/Cog/VM/VM.r2313/) as this involved substantial changes to method lookup/inline cacheing machinery and there could easily be bugs. The tests run, but they're insubstantial compared e.g. to a full coverage test. best Eliot (repeat with fixed email address: squeakfountation => squeakfoundation) On Sat, Sep 25, 2010 at 9:20 PM, < squeak-dev-noreply(a)lists.squeakfoundation.org> wrote: > > Eliot Miranda uploaded a new version of VMMaker to project VM Maker: > http://www.squeaksource.com/VMMaker/VMMaker-oscog.33.mcz > > ==================== Summary ==================== > > Name: VMMaker-oscog.33 > Author: eem > Time: 25 September 2010, 7:13:51 am > UUID: 733b7c50-b973-4ca0-9831-5c84d09032bf > Ancestors: VMMaker-oscog.32 > > OSCogVM: > Support object-as-method: > Eagerly evaluate the interpreter version of a primitive > to ease the object-as-method implementation and to > improve interpreter performance. > Refuse to enter anything that isn't a CompiledMethod > into the method-lookup cache to avoid open PICs having > to check for valid compiled methods. > Have various places check for isOopCOmpiledMethod: > rather than isCompiledMethod: to allow SmallIntegers to > be used as methods. > Interpreter: > Have various places check for isOopCOmpiledMethod: > rather than isCompiledMethod: to allow SmallIntegers to > be used as methods. > Slang: > support super sends by expanding them at translation > time. This allows CoInterpreter>>addMethodToCache > to avoid cacheing non-compiled methods via a super > send, avoiding duplicating SrackInterpreter's method. > >

Sept. 26, 2010

Re: [Pharo-project] [Vm-dev] VM Maker: VMMaker-oscog.33.mcz

by Eliot Miranda

I would appreciate anyone interested in objects-as-methods on Cog pounding on the latest Cog VMs (http://www.mirandabanda.org/files/Cog/VM/VM.r2313/) as this involved substantial changes to method lookup/inline cacheing machinery and there could easily be bugs. The tests run, but they're insubstantial compared e.g. to a full coverage test. best Eliot On Sat, Sep 25, 2010 at 9:20 PM, < squeak-dev-noreply(a)lists.squeakfoundation.org> wrote: > > Eliot Miranda uploaded a new version of VMMaker to project VM Maker: > http://www.squeaksource.com/VMMaker/VMMaker-oscog.33.mcz > > ==================== Summary ==================== > > Name: VMMaker-oscog.33 > Author: eem > Time: 25 September 2010, 7:13:51 am > UUID: 733b7c50-b973-4ca0-9831-5c84d09032bf > Ancestors: VMMaker-oscog.32 > > OSCogVM: > Support object-as-method: > Eagerly evaluate the interpreter version of a primitive > to ease the object-as-method implementation and to > improve interpreter performance. > Refuse to enter anything that isn't a CompiledMethod > into the method-lookup cache to avoid open PICs having > to check for valid compiled methods. > Have various places check for isOopCOmpiledMethod: > rather than isCompiledMethod: to allow SmallIntegers to > be used as methods. > Interpreter: > Have various places check for isOopCOmpiledMethod: > rather than isCompiledMethod: to allow SmallIntegers to > be used as methods. > Slang: > support super sends by expanding them at translation > time. This allows CoInterpreter>>addMethodToCache > to avoid cacheing non-compiled methods via a super > send, avoiding duplicating SrackInterpreter's method. > >

Sept. 26, 2010

[Pharo-project] MuTalk: Mutation Testing for Pharo Smalltalk

by Gabriel Brunstein

Hi! I just want to let you know that MuTalk is available for Pharo-Dev versions 1.0 and 1.1 you can load it with monticello from http://www.squeaksource.com/MutationTesting MutationTesting-NicolasChillo.101 for loading last version in Pharo 1.1 (thanks to Francisco Ortiz PeÃ±aloza) MutationTesting-GabrielBrunstein.97 for loading last verion in Pharo 1.0 More info here: http://code.google.com/p/mutalk/ We developed it with Nicolas Chillo for our career thesis but we will continue working on it. Basically, Mutation Testing is a technique for measuring and improving tests quality. All suggestions are welcome. Bests, Gabriel PS: it doesn't work with CogVM but I think that this problem will be solved with Pharo 1.2 (we must adapt it to work there).

Sept. 26, 2010

Re: [Pharo-project] #copy and friends

by Levente Uzonyi

On Sat, 25 Sep 2010, Schwab,Wilhelm K wrote: > copy > "Answer another instance just like the receiver. Subclasses typically override postCopy; they typically do not override shallowCopy. Copy is a template method in the sense of Design Patterns. So do not override it. Override shallowCopy instead. Pay attention that normally you should call postCopy of your superclass too." It should be: Override postCopy instead. Levente > > ^self shallowCopy postCopy > > > > shallowCopy > "Answer a copy of the receiver which shares the receiver's instance variables. It should never be overridden. I'm invoked from the copy template method. Subclasses that need to specialize the copy should specialize the postCopy hook method." > > > The references to #postCopy are probably valid, but the comments above can't both be correct. Right?? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 26, 2010

[Pharo-project] #copy and friends

by Schwab,Wilhelm K

copy "Answer another instance just like the receiver. Subclasses typically override postCopy; they typically do not override shallowCopy. Copy is a template method in the sense of Design Patterns. So do not override it. Override shallowCopy instead. Pay attention that normally you should call postCopy of your superclass too." ^self shallowCopy postCopy shallowCopy "Answer a copy of the receiver which shares the receiver's instance variables. It should never be overridden. I'm invoked from the copy template method. Subclasses that need to specialize the copy should specialize the postCopy hook method." The references to #postCopy are probably valid, but the comments above can't both be correct. Right?? Bill

Sept. 25, 2010

Re: [Pharo-project] In Smalltalk you can't loose code... hum

by FranÃ§ois Tanguy

Le 25 sept. 2010 Ã 21:43, George Herolyants a Ã©crit : > Hi, > > 2010/9/25 FranÃ§ois Tanguy <francois.tanguy(a)gmail.com>: >> Hi, >> >> the statement is true when the code is saved in the browser. >> But in a workspace or in the script manager that is not true. > > You can save a workspace into a file and it will be renewed each time > you press Cmd+S. Here is what I did: 1) Open a workspace / save the image 2) edit the workspace / save Cmd + S 3) quit Pharo without saving 4) Open pharo -> the workspace is empty > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 25, 2010

Re: [Pharo-project] In Smalltalk you can't loose code... hum

by FranÃ§ois Tanguy

Le 25 sept. 2010 Ã 21:53, StÃ©phane Ducasse a Ã©crit : > > On Sep 25, 2010, at 9:25 PM, FranÃ§ois Tanguy wrote: > >> Hi, >> >> the statement is true when the code is saved in the browser. >> But in a workspace or in the script manager that is not true. >> >> Actually it is a feature request: You can't loose code even when you are working in the script browser. > > check if you can find a way and I'm sure that the maintainer of scriptmanager will integrate it. > I always prefer to define methods so I never use script or workspace to write anything useful. In my case, I wrote some crap and got an endless loop... Had to quit the image and lost some code. But I kind of like the script manager to write codes that build models or examples to remind me how to do some stuff. I will have a look at the script manager and hope we can come up with a solution. At least when Cmd + S is pressed, the minimum would be to save the code. > >> >> Because in the script manager has a save capability, would it be difficult to write the changes into the changes files ? > > the problem is that the change files logic is old and it works 'well' for what it should but extending it will break other part. > This is why slowly we will have to think to get something better. > > >> >> Francois >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 25, 2010

[Pharo-project] Implement Keyboard focus on a custom morph when have rounded corners

by nullPointer

IÂ´m developing new widgets, integrateds in Polymorph. But when I try implement the keyboard focus appearance fails when the widget have rounded corners: http://forum.world.st/file/n2713899/RoundedCorner.png I imagine something miss, but I donÂ´t know what. I implement the keyboard focus with drawSubmorphsOn: aCanvas super drawSubmorphsOn: aCanvas. self hasKeyboardFocus ifTrue: [self drawKeyboardFocusOn: aCanvas]. Many thanks for the help :)) -- View this message in context: http://forum.world.st/Implement-Keyboard-focus-on-a-custom-morph-when-have-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 25, 2010

Re: [Pharo-project] Webpage for research paper about Pharo?

by Alexandre Bergel

Makes sense. However, I do not want to emphasize on the past with old papers. I am now working on the webpage Cheers, Alexandre On 25 Sep 2010, at 03:10, StÃ©phane Ducasse wrote: > guys > > all my papers are using Smalltalk (visualworks, squeak mainly so far) as a research vehicule. You can use them to do marketing around smalltalk because there are good papers in prestigious venues. Please do not have the time. > > Now pharo has the right to mention the papers using pharo on the pharo web site. > > Stef > > On Sep 25, 2010, at 12:20 AM, Sean P. DeNigris wrote: > >> >> How about putting the papers on both sites ;-) >> >> Sean >> -- >> View this message in context: http://forum.world.st/Webpage-for-research-paper-about-Pharo-tp2549096p2606… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 25, 2010