- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3866 in pharo: [Failing Test] 1.3 ReleaseTest.testUndeclared

by pharo＠googlecode.com

Updates: Status: FixToInclude Comment #1 on issue 3866 by marcus.d...(a)gmail.com: [Failing Test] 1.3 ReleaseTest.testUndeclared http://code.google.com/p/pharo/issues/detail?id=3866 cs attached fixes all undeclareds Attachments: UndeclaredRefsFix.1.cs 3.0 KB

March 28, 2011

[Pharo-project] Which methods are really not executed?

by Mariano Martinez Peck

Hi folks. I would like to know which are the messages that are not really executed, thus not being intercepted by proxies. So far, I know: 1) MessageNode >> initialize MacroSelectors := #( ifTrue: ifFalse: ifTrue:ifFalse: ifFalse:ifTrue: and: or: whileFalse: whileTrue: whileFalse whileTrue to:do: to:by:do: caseOf: caseOf:otherwise: ifNil: ifNotNil: ifNil:ifNotNil: ifNotNil:ifNil:). those are inlined by the compiler... 2) Special shorcut bytecodes that are in "Smalltalk specialSelectors" / "ParseNode classVarNamed: 'StdSelectors'" / "Smalltalk specialObjectsArray at: 24" Here I have a question...if I understand correctly, in this list of selectors there are 3 cases: 2.1) methods may or may not be executed depending on the receiver/arguments. For example 1 + 2 will never send the message #+ to 1. but 1 + 'mariano' will do. 2.2) methods that are NEVER sent, like #class and #== 2.3) methods that are ALWAYS sent, like #new, #next, #nextPut:, #size, etc. So...did I understand correclty this part? are there more cases where a message may not be really executed? thanks Mariano

March 28, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Camillo Bruni

>>> I don't care. I have it working for my "usage". This was just an example. >>> >>> And don't compare #class with all the boolean methods like #ifNil: and >>> friends or the bytecodes for integer operations....I think #class is >> sent >>> far less times than those... >>> >> >> Yes. and i predict that performance impact in macro benchmarks, where >> you running normal code >> (which not sending this message intentionally in a loop) will be at >> the noise level magnitude. >> > > So...what about doing something more real...for example, run all the > testcases and compare time. > Wouldn't that be a good "benchmark" ? sounds already better. make sure to run it something like 100 times, get the average and the standard deviation. otherwise the results don't provide much information. > BTW, can I run all test from code? (not using the TestRunner UI) something like the following code should do it. TestCase allSubclasses do: [ :cls| cls isAbstract ifFalse: [cls run]].

March 28, 2011

Re: [Pharo-project] [Seaside] rack/wsgi/ring for smalltalk

by Janko MivÅ¡ek

Hi Sean, What exactly would you like to achieve with Rack-like middleware? As I understood Rack is mostly a HTTP message composing/parsing framework, so in short the HTTPRequest and HTTPResponse classes with all accompanying infrastructure. We have that already in all our HTTP projects, from Swazoo to WebClient and Zync, etc. What would be nice would be an unified HTTP messaging for all web projects... Best regards Janko On 28. 03. 2011 01:55, Sean Allen wrote: > On Sun, Mar 27, 2011 at 2:42 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> >> On 27 Mar 2011, at 19:13, Sean Allen wrote: >> >>> Is there a smalltalk equivalent for rack/wsgi/ring etc out there? >>> >>> I have an idea I'm going to play with that would be best served by >>> building on something like rack. >>> If there isn't one already, I'll implement one first and then move on >>> to the idea that builds on it. >>> If there is one, I'd rather see if it meets my needs and use it. >>> >>> Any pointers to anything appreciated. >>> >>> For anyone not familiar with rack et al: >>> >>> They are basically' middleware' layers providing a standard interface >>> between webservers and applications. >>> Middleware is a little deceptive... a better description might be that >>> it is an interface that allows you to >>> hook into between a webserver and other end points by either hooking >>> up an application or middleware >>> ( authentication, file serving ) that can be composed together as part >>> of a specific application. >>> >>> http://rack.rubyforge.org/ >>> https://github.com/mmcgrana/ring >>> http://www.wsgi.org/wsgi/ >> >> Might be cool and useful. >> I guess that Seaside's WAServerAdaptor concept comes very close. >> It has the advantage that it's proven in the field, supporting many servers in different Smalltalk implementations. >> But maybe you already knew this. >> > > WAServerAdaptor isn't really much like ring, rack et al. > But it does put the thought into my mind that it would be interesting > down the road to > try and take the Seaside infrastructure and work something like rack into it. > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 28, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Mariano Martinez Peck

On Fri, Mar 25, 2011 at 8:27 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 25 March 2011 19:22, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > > > On Fri, Mar 25, 2011 at 7:08 PM, Toon Verwaest <toon.verwaest(a)gmail.com> > > wrote: > >> > >>>> What do you think? > >>> > >>> I am for... for the JIT is is a monomorphic send to a primitive, so the > >>> IC will be very effective > >>> and should take care that the lookup is actually almost never done. > (and > >>> the lookup is the > >>> only thing the #class bytecode saves, as the target method is a > >>> primitive). > >> > >> I think that programmers should have the illusion that the VM interacts > >> with the system through message sends. By being able to overwrite this > >> particular message you break this illusion. The VM will just fetch the > real > >> class; but the user doesn't get access to it anymore. Telling the system > >> that this particular message shouldn't be overwritten is probably a good > >> thing. > >> > >> If you want to overwrite the method class, maybe your tools should send > >> another message than class in the first place? > > > > Of course I can do that. I can also do > > > > (ParseNode classVarNamed: 'StdSelectors') removeKey: #class > ifAbsent: > > []. > > Compiler recompileAll. > > > > I don't care. I have it working for my "usage". This was just an example. > > > > And don't compare #class with all the boolean methods like #ifNil: and > > friends or the bytecodes for integer operations....I think #class is > sent > > far less times than those... > > > > Yes. and i predict that performance impact in macro benchmarks, where > you running normal code > (which not sending this message intentionally in a loop) will be at > the noise level magnitude. > So...what about doing something more real...for example, run all the testcases and compare time. Wouldn't that be a good "benchmark" ? BTW, can I run all test from code? (not using the TestRunner UI) > > > > >> > >> I do however agree that many other optimizations become slightly > >> superfluous, such as bytecodes for integer operations ... that somehow > seems > >> like compile-time inline-cached behavior without the ability to flush > the > >> cache :) > >> > >> cheers, > >> Toon > >> > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

March 28, 2011

[Pharo-project] PharoCasts with experts

by laurent laffont

Hi, Actually I'm training remotely a developer on Pharo using Skype and TeamViewer. This guy records all sessions for its own purpose and I like the idea. For PharoCasts I would like to record 30mn to 1 hour sessions (as I know you don't have time) with an expert who shows us real code, explaining a framework / programming style / pattern while programming some examples (in the spirit of PharoCasts, and may be http://forum.world.st/Screencast-proposition-Watch-someone-read-code-td3244…) Right now I'm thinking about: - Mariano on DBXTalk - Gary on Polymorph - Igor on VM debugging or FFI / NativeBoost (for example interfacing with http://id3lib.sourceforge.net/ or other lib) - Lukas on Magritte or PetitParser - Dale on Metacello - Nicolas on Iliad - Janko on Aida/Web and all that I forgot ..... I'm sure plenty of people would like their open-source project to be more known. This may be an opportunity. How to do this: contact me if you wish to do that so we can choose an hour that match our respective calendars and agree on tools used (skype, google video chat, vnc, teamviewer, ....) - I will care about video stuff. Just talk and code :) Anyone ? Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

March 28, 2011

Re: [Pharo-project] [Seaside] rack/wsgi/ring for smalltalk

by Sean Allen

On Sun, Mar 27, 2011 at 2:42 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 27 Mar 2011, at 19:13, Sean Allen wrote: > >> Is there a smalltalk equivalent for rack/wsgi/ring etc out there? >> >> I have an idea I'm going to play with that would be best served by >> building on something like rack. >> If there isn't one already, I'll implement one first and then move on >> to the idea that builds on it. >> If there is one, I'd rather see if it meets my needs and use it. >> >> Any pointers to anything appreciated. >> >> For Â anyone not familiar with rack et al: >> >> They are basically' middleware' layers providing a standard interface >> between webservers and applications. >> Middleware is a little deceptive... a better description might be that >> it is an interface that allows you to >> hook into between a webserver and other end points by either hooking >> up an application or middleware >> ( authentication, file serving ) that can be composed together as part >> of a specific application. >> >> http://rack.rubyforge.org/ >> https://github.com/mmcgrana/ring >> http://www.wsgi.org/wsgi/ > > Might be cool and useful. > I guess that Seaside's WAServerAdaptor concept comes very close. > It has the advantage that it's proven in the field, supporting many servers in different Smalltalk implementations. > But maybe you already knew this. > WAServerAdaptor isn't really much like ring, rack et al. But it does put the thought into my mind that it would be interesting down the road to try and take the Seaside infrastructure and work something like rack into it.

March 27, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by Stuart Herring

I definitely use them - I like being able to locate the windows instantly by colour. And a less practical reason is that the grey default themes always make me feel depressed. Programming shouldn't be grey and boring, it should be fun ;) A new, supported colourised theme would be a wonderful thing - particularly if there were settings to choose the colour scheme. I like the coloured windows so much that I've been tempted to go back to Squeak - right up until the overloaded world menu reminds me why I prefer Pharo. Regards, Stuart On Sat, Mar 26, 2011 at 7:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > just out of curiosity who is using SoftSqueak and Standard Squeak theme? > I know that lukas like colored windows now may be specific new style with this behavior could be done? > > Stef >

March 27, 2011

[Pharo-project] [COTDC] 37 - MCPatcher

by laurent laffont

Today: MCPatcher Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

March 27, 2011

Re: [Pharo-project] A stupid magritte question :(

by Lukas Renggli

Hi Stef, You can try with MAToManyScalarRelationDescription where the #reference: description is a MAStringDescription. Philippe added this many years ago, but I don't think that it has seen much use. Lukas On 27 March 2011 20:56, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi all and (lukas in particular) > > I have an object which hold a list of strings and I would like to describe it using magritte so I thought that I should use > a MAContainer. > > But how should I specify the fact that the elements are of a specific class? > > Stef > -- Lukas Renggli www.lukas-renggli.ch

March 27, 2011