September 2010 - Pharo-users

Re: [Pharo-users] ifTrue not acting as a polymorphic message?
by Marcus Denker Sept. 24, 2010

Sept. 24, 2010

Hello, > > While I was thinking on an exercise to give to the students I though about developing a three-valued logic, creating the TTrue, TFalse, and TUnknown, whos instances understood some methods such as #ifTrue: #ifFalse: and so on. > > My surprise came when I discovered that the ifTrue: method only work for the True and False instances of Smalltalk, being unable to define a method named ifTrue: > > For what I saw the problem is that, on non boolean receivers, the method is not even evaluated to see if the receiver can understand it, but it automatically triggers the message #mustBeBoolean > > So my question is, why does it do this? Is there a way to use ifTrue: really as a method? > Is there a way that I can make ifTrue: to work with any Class and not just Booleans? > The reason is that ifTrue: is compiled by the smalltalk-to-bytecode compiler to a test-and-jump bytecode. So ^1 + 2 ifTrue: ['true'] is compiled to: 17 <76> pushConstant: 1 18 <77> pushConstant: 2 19 <B0> send: + 20 <99> jumpFalse: 23 21 <20> pushConstant: 'true' 22 <90> jumpTo: 24 23 <73> pushConstant: nil 24 <7C> returnTop In smalltalk, we do not know at compile time the type of any expression. So we can not build a compiler that does the jump for the case that the expression is a boolean and send the message else. We know the class of the result of an expression only at runtime, not at compile time. So the solution takes was to make some selectors special. ifTrue: is *always* compiled to a jump bytecode. This in turn means that it can not be used for any other purpose. If you implement it in your own class, it will never be called. (I alwasy wanted to look into the question if the vm could not just re-send ifTrue: instead of giving the useless error message...) One possible way around this (for experiments) is to change the compiler to always send ifTrue: and never do the jump bytecode. The image gets slow, though (but it can be done). Another, more practical solution is to just do the change for the classes you are experimenting with and use a hacked second compiler for those (we did this with the NewCompiler in the past when experimenting with different things). Or you could change the inlining logic of the compiler to not inline ifTrue just for your package, or depending on a pragma in the method. In Opal (the new compiler, sadly not yet a drop-in replacement, but soon), the place to do that is quickly found. There is a visitor that translates AST to bytecode. It has a method acceptMessageNode: aMessageNode aMessageNode isInlineIf ifTrue: [^ self emitIfNode: aMessageNode]. aMessageNode isInlineIfNil ifTrue: [^ self emitIfNilNode: aMessageNode]. aMessageNode isInlineAndOr ifTrue: [^ self emitAndOrNode: aMessageNode]. aMessageNode isInlineWhile ifTrue: [^ self emitWhileNode: aMessageNode]. aMessageNode isInlineToDo ifTrue: [^ self emitToDoNode: aMessageNode]. aMessageNode isInlineCase ifTrue: [^ self emitCaseNode: aMessageNode]. ^ self emitMessageNode: aMessageNode Easy. The old smalltalk compiler, I always get headaches looking at it. I guess #transformIfNil: would be the starting point to look at. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Digest] Opal Compiler
by StÃ©phane Ducasse Sept. 24, 2010

Sept. 24, 2010

A little digest of the Opal activity. Thanks marcus, jorge and jb Name: OpalCompiler-Core-MarcusDenker.39 Author: MarcusDenker Time: 22 September 2010, 12:49:03 pm UUID: f0990355-584c-4f3e-b72e-4ef73c915e20 Ancestors: OpalCompiler-Core-JorgeRessia.38 -> escaping now destinguishes between escapingRead and escapingWrite -> write on an escapingRead Temp makes it escapingWrite, too -> fixed ASTranslator to correctly use the copying vars of the outer scope when calling IRBuilder to create a block -> Cleanups Name: OpalCompiler-Core-JorgeRessia.41 Author: JorgeRessia Time: 22 September 2010, 7:28:07 pm UUID: a22e64f9-0181-45a0-a531-2b929c2bd969 Ancestors: OpalCompiler-Core-MarcusDenker.40 - fixing optimezed blocks remote temps Name: OpalCompiler-Core-JorgeRessia.42 Author: JorgeRessia Time: 23 September 2010, 10:48:37 am UUID: b144fc34-6ed0-4acd-a538-3dd8fa386143 Ancestors: OpalCompiler-Core-JorgeRessia.41 Fixing optimized Block analysis Name: OpalCompiler-Tests-JorgeRessia.41 Author: JorgeRessia Time: 23 September 2010, 11:26 am UUID: f0c522bc-5b78-442f-942c-181e4fe03f98 Ancestors: OpalCompiler-Tests-JorgeRessia.40 New cases for the optimized blocks Name: OpalCompiler-Tests-JorgeRessia.43 Author: JorgeRessia Time: 23 September 2010, 2:29:09 pm UUID: dcca39e4-660f-4a9e-9349-021743f3773b Ancestors: OpalCompiler-Tests-JorgeRessia.42 Lexical Analysis and Closure Analysis green tests Name: OpalCompiler-Core-JorgeRessia.43 Author: JorgeRessia Time: 23 September 2010, 2:02:56 pm UUID: 8208019f-9941-4279-b969-ed5c63a92fc2 Ancestors: OpalCompiler-Core-JorgeRessia.42 Fixing optimized Block analysis Name: OpalCompiler-Core-JorgeRessia.45 Author: JorgeRessia Time: 23 September 2010, 7:20:04 pm UUID: e3dbc461-ba42-4153-af21-bf321b07f131 Ancestors: OpalCompiler-Core-JorgeRessia.44 Refactoring and fixing code ==================== Summary ==================== Name: OpalCompiler-Core-JorgeRessia.44 Author: JorgeRessia Time: 23 September 2010, 6:10:02 pm UUID: 971894ca-6ca7-4f21-9ac2-bb1c47be0958 Ancestors: OpalCompiler-Core-JorgeRessia.43 - Fixed problems with optimized block in the semantic analysis - Fixed bug with the copied temp in a block in the semantic analysis. - new test for special cases of optimized loops. - fixed ASTClosureAnalysisTest for testing the copied values.

1 0

ifTrue not acting as a polymorphic message?
by Alan Rodas Sept. 24, 2010

Sept. 24, 2010

First of all, hi to everybody. This is my first time posting to this list, and as the nettiquette rules says I introduce myself. I'm a student from the Universidad Nacional de Quilmes, in Quilmes, Buenos Aires, Argentina. So I beg for you to apologize my bad English. I'm currently the teachers assistent at Tecnicas Avanzadas de Programacion (Object Oriented Programming) Well, that's pretty much it. Second of all I would like to thank and congratulate the team behind Pharo. It's by far my favorite Smalltalk environment, although I miss some features from VisualWorks (Future discussion maybe :-) ) -------------------------------- Now, to my problem. While I was thinking on an exercise to give to the students I though about developing a three-valued logic, creating the TTrue, TFalse, and TUnknown, whos instances understood some methods such as #ifTrue: #ifFalse: and so on. My surprise came when I discovered that the ifTrue: method only work for the True and False instances of Smalltalk, being unable to define a method named ifTrue: For what I saw the problem is that, on non boolean receivers, the method is not even evaluated to see if the receiver can understand it, but it automatically triggers the message #mustBeBoolean So my question is, why does it do this? Is there a way to use ifTrue: really as a method? Is there a way that I can make ifTrue: to work with any Class and not just Booleans? Thanks in advance. -- Alan Rodas Bonjour

1 0

Re: [Pharo-users] [Pharo-project] Changes in external packages for Pharo 1.2
by StÃ©phane Ducasse Sept. 23, 2010

Sept. 23, 2010

keep it simple for now. Let us focus on fixing 1.2 > Hi folks. I would like to write now the changes for the development image for Pharo 1.2. > > Right now I have the following: > > - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. > - Add Memory Monitor tool from Alexandre Bergel. > - Add AutoTest from Laurent Laffont. > - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. > > For any package we include, it would be AWESOME to have: > - tests > - a Metacello configuration > > So, questions: > > 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) > 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. > 3) do you think there are more packages/projects we should include? What about, for example: > Keep that for later. > - WorkingSet from Romain Robbes > - Algernon (still doesn't work in 1.1) > - TDDFacilties from Hernan Wilkinson > - SimpleLogger from German Arduino > > I know this is not Dev, but I hope in Pharo1.2 we will have: > - The new method finder from Benjamin that mixes both, and remove the old ones. > - The new RecentSubmisons, and remove the old one. > > Thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Ffi in Pharo 1.1
by Bruce Haugland Sept. 22, 2010

Sept. 22, 2010

I noticed in Pharo 1.1 that the loadFFI script in the script loader is no longer there. How can I load FFI into Pharo 1.1. I noticed that the shared library is there but that there are no supporting FFI Classes. Thanks for the Help. Bruce

3 7

Changes in external packages for Pharo 1.2
by Mariano Martinez Peck Sept. 22, 2010

Sept. 22, 2010

Hi folks. I would like to write now the changes for the development image for Pharo 1.2. Right now I have the following: - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. - Add Memory Monitor tool from Alexandre Bergel. - Add AutoTest from Laurent Laffont. - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. For any package we include, it would be AWESOME to have: - tests - a Metacello configuration So, questions: 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. 3) do you think there are more packages/projects we should include? What about, for example: - WorkingSet from Romain Robbes - Algernon (still doesn't work in 1.1) - TDDFacilties from Hernan Wilkinson - SimpleLogger from German Arduino I know this is not Dev, but I hope in Pharo1.2 we will have: - The new method finder from Benjamin that mixes both, and remove the old ones. - The new RecentSubmisons, and remove the old one. Thanks Mariano

1 0

Printing documents
by Linus De Meyere Sept. 22, 2010

Sept. 22, 2010

Hey all, Is there a way to drive a printer from a pharo environment? I would like to know if it's possible to generate a pdf and instruct the printer to print it. Any advice? Thanks in advance, Linus

4 3

Re: [Pharo-users] Recent Submissions
by Benjamin Van Ryseghem Sept. 21, 2010

Sept. 21, 2010

The first step is to successfully update MethodReference without blowing the whole system :) I have to discuss about that with Stef Ben

1 0

Re: [Pharo-users] [Pharo-project] Recent Submissions
by Marcus Denker Sept. 21, 2010

Sept. 21, 2010

On Sep 21, 2010, at 1:01 PM, Mariano Martinez Peck wrote: > Same question.....this RecenSubmissions will be part of PharoCore isn't it? Yes. No need to have yet another package. > is it already integrated? > I think not yet. > There is no need to update PharoDev building? > No. > thanks > > Mariano > > On Mon, Jul 19, 2010 at 11:31 PM, Benjamin Van Ryseghem <benjamin.vanryseghem(a)gmail.com> wrote: > Ok Stef, so i've separated my work from the Tool-Browser class (there is a bug to fix into the RecentMessageSet class in order to remove useless multiples entries) > > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'RecentSubmissions'; > load > > A way to open the alternate viewer is by doing: > > RecentSubmissions openInWorld > > Ben > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Recent Submissions
by Benjamin Van Ryseghem Sept. 21, 2010

Sept. 21, 2010

Ok Stef, so i've separated my work from the Tool-Browser class (there is a bug to fix into the RecentMessageSet class in order to remove useless multiples entries) Gofer new squeaksource: 'PharoTaskForces'; package: 'RecentSubmissions'; load A way to open the alternate viewer is by doing: RecentSubmissions openInWorld Ben

2 1