- Pharo-dev - lists.pharo.org

Re: [Pharo-project] A small quiz: longest selector

by Sean P. DeNigris

Pavel Krivanek-3 wrote > > Before you will write an oneliner to get the exact result, try to make a > tip ;-) > #subclass:instanceVariableNames:classVariableNames:poolDictionaries:category: ? probably not, but that's the first thing that came to mind... -- View this message in context: http://forum.world.st/A-small-quiz-longest-selector-tp4647311p4647318.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 13, 2012

Re: [Pharo-project] A small quiz: longest selector

by Benjamin

I will have bet on a Morphic method, but the result is surprising :) Ben On Sep 13, 2012, at 7:15 PM, Pavel Krivanek wrote: > Hi, > > I've got a small quiz question for fun: What is the length of the > longest method selector in Pharo? > > Before you will write an oneliner to get the exact result, try to make a tip ;-) > > Cheers, > -- Pavel >

Sept. 13, 2012

[Pharo-project] [update 2.0] #20282

by Esteban Lorenzano

20282 ----- Issue 6661: remove Rpackage package from monticello http://code.google.com/p/pharo/issues/detail?id=6661 Issue 6666: RPackageSet missing methods http://code.google.com/p/pharo/issues/detail?id=6666

Sept. 13, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 344 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 13, 2012

[Pharo-project] A small quiz: longest selector

by Pavel Krivanek

Hi, I've got a small quiz question for fun: What is the length of the longest method selector in Pharo? Before you will write an oneliner to get the exact result, try to make a tip ;-) Cheers, -- Pavel

Sept. 13, 2012

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

by Igor Stasenko

On 13 September 2012 14:06, Guy Hylton <guygantuan(a)gmail.com> wrote: >> just give me your squeaksource account, so i can add you as developer. > > grh > done. >> Oh, yeah.. >> and this sort of problems (with re-initialization). >> It would be nice to have them solved automatically. >> I think it was bad idea to cache fields in NBExternalStructure. >> It would be better to solve that differently. > I expect that is more complicated than it first appears, but it will be good > opportunity to look how the existing caching mechanism works. > > Thanks, Guy -- Best regards, Igor Stasenko.

Sept. 13, 2012

[Pharo-project] FileSystem-Git GoogleGroup and mailing list

by Max Leske

For those interested in FileSystem-Git there is now a dedicated GoogleGroup / mailing list: https://groups.google.com/forum/#!forum/smalltalk-git / smalltalk-git(a)googlegroups.com. Max

Sept. 13, 2012

[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

by Guy Hylton

> just give me your squeaksource account, so i can add you as developer. grh > Oh, yeah.. > and this sort of problems (with re-initialization). > It would be nice to have them solved automatically. > I think it was bad idea to cache fields in NBExternalStructure. > It would be better to solve that differently. I expect that is more complicated than it first appears, but it will be good opportunity to look how the existing caching mechanism works. Thanks, Guy

Sept. 13, 2012

[Pharo-project] Proxy Exception settings

by Santiago Bragagnolo

Hi all. I just added a setting to specify exceptions for HTTP proxy. http://code.google.com/p/pharo/issues/detail?id=6663#makechanges regards Santiago.

Sept. 13, 2012

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

by Igor Stasenko

Oh, yeah.. and this sort of problems (with re-initialization). It would be nice to have them solved automatically. I think it was bad idea to cache fields in NBExternalStructure. It would be better to solve that differently. On 13 September 2012 09:18, Guy Hylton <guygantuan(a)gmail.com> wrote: > Igor, > >> P.S. The configuration is freshly-baked, i didn't even checked if it >> loads cleanly or not.. >> so, i don't recommend updating it in image with your precious code :) > > I have tried loading your updated Configuration into Pharo1.4 #14438 and it > loaded ok, but as a NativeBoost beginner it took me sometime to work out > that I needed to run NBFFICallout>>initialize to get the new NB types > registered. I found that this could be achieved using a postLoadDoIt > message in the Configuration ... > > spec package: 'NativeBoost-Core' with: [ > spec > file: 'NativeBoost-Core-IgorStasenko.75'; > postLoadDoIt: #postloadForCore ]. > >> Gofer it >> squeaksource: 'NativeBoost'; >> package: 'ConfigurationOfNativeBoost'; >> load. > >> (ConfigurationOfNativeBoost project version: '1.4' ) load > >> P.P.S. i would really like some help with testing what i did, >> including writing some more tests to cover type system more >> broadly (now since type names follow certain naming rule, many >> different types can be checked without much coding) > > > Some of the tests failed after the update because it was necessary to > rebuildAccessors for a couple of the structures used so that they referred > to the new NB types. > > Although this is a trivial change I would like to try and help your efforts > with some more tests and documentation, but how should I submit them? > Should I follow the "HowToContribute" procedure on the Pharo website? > > Thanks, Guy -- Best regards, Igor Stasenko.

Sept. 13, 2012