November 2011 - Pharo-users

Re: [Pharo-users] permutations / combinations implementation

by Runar Jordahl

You can look at #combinations:atATimeDo: (found in 1.2.1). This method does "combinations" ( http://en.wikipedia.org/wiki/Combination ), but not permutations ( http://en.wikipedia.org/wiki/Permutations ). Runar Jordahl 2010/11/15 Tudor Girba <tudor.girba(a)gmail.com>: > Hi, > > Is there an implementation of permutations and combinations of a collection? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Presenting is storytelling." > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

Nov. 2, 2011

Re: [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Norbert Hartl

Am 31.10.2011 um 11:54 schrieb StÃ©phane Ducasse: > Now the free items with probably igor involvement > - Multiwindowing support > - Fully working multithreaded FFI with ***Documentation*** > - Filesystem fix and integration > - Integration of OPAL > - RPackage integration I like to add environments so we can have multiple versions in the same image and get rid of default global state. I think you have that already on your mind even with separate object memories. Norbert

Nov. 2, 2011

Re: [Pharo-users] Exception style

by Mariano Martinez Peck

On Tue, Nov 1, 2011 at 1:35 AM, Jeff Gray <jeff(a)rogerthedog.com> wrote: > I have just watched James Robertson's Exception screencast on exceptions in > Pharo. > I haven't really bothered with it previously as I have only played around > and haven't done anything in anger. > My commercial background in Java and C# has been with quite different > styles > of exception handling. > Java was always cluttered with exception handling and re-throwing all > through the code whereas in .net it was very much a 'let it bubble up to > the > container' approach. > > Although James screencast shows the mechanics of exceptions I'm wondering > what is a normal exception handling strategy in Pharo? > Imagine that in Pharo they would all be "runtime" exception (non-checked was called in Java? I don't remember)... well, that means that the "throws" is not part of the signature and hence a caller doesn't HAVE to mandatory handle the exception. To handle an exception you can do: [ Transcript show: 'this is the code that I want to execute and may trhow an aexception' ] on: ThisParticularError do: [ self manageThisParticularError ] You can handle Error if you want something more general. You can send #resume to an exception (if possible), etc, etc ec. As Stef said, read the chapter and ask if you have further questions: https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.p… > Obvoiusly tutorial code doesn't want to get bogged down with exceptions > when > trying to teach a specific aspect in smalltalk/pharo/oo etc but I'm yet to > see tutorial example code that handles exceptions. > > > -- > View this message in context: > http://forum.world.st/Exception-style-tp3962162p3962162.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Nov. 1, 2011

Re: [Pharo-users] Exception style

by StÃ©phane Ducasse

Hi jeff It depends. What I saw in the software developed by Hernan wilkinson to manage conferences (Patagonia) is that hernan defines a lot of specific exceptions. In Core pharo we are a bit learning and cleaning the menu pop up to indicate error. It should be an error and trapped by the UI manager. I guess that experts will react on your questions. Now I do not know if you know the exceptions chapter http://www.pharobyexample.org/ Stef On Nov 1, 2011, at 1:35 AM, Jeff Gray wrote: > I have just watched James Robertson's Exception screencast on exceptions in > Pharo. > I haven't really bothered with it previously as I have only played around > and haven't done anything in anger. > My commercial background in Java and C# has been with quite different styles > of exception handling. > Java was always cluttered with exception handling and re-throwing all > through the code whereas in .net it was very much a 'let it bubble up to the > container' approach. > > Although James screencast shows the mechanics of exceptions I'm wondering > what is a normal exception handling strategy in Pharo? > Obvoiusly tutorial code doesn't want to get bogged down with exceptions when > trying to teach a specific aspect in smalltalk/pharo/oo etc but I'm yet to > see tutorial example code that handles exceptions. > > > -- > View this message in context: http://forum.world.st/Exception-style-tp3962162p3962162.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Nov. 1, 2011

Re: [Pharo-users] Creating a FSReference

by Luc Fabresse

Hi Sean, 2011/11/1 Sean P. DeNigris <sean(a)clipperadams.com> > What's the easiest way to create a reference to, say, /dev from a string? > > I came up with "FSFilesystem disk root resolveString: '/dev'." Anything > better? > I guess those ones also make it: FSFilesystem disk root / 'dev' (FSPath / 'dev') asReference Cheers, #Luc > > Also, what's the difference between > FSReference>> > resolve: > resolveString: ? > > They both seem to do the same thing in this case. > > Thanks. > Sean > > -- > View this message in context: > http://forum.world.st/Creating-a-FSReference-tp3962401p3962401.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Nov. 1, 2011

Creating a FSReference

by Sean P. DeNigris

What's the easiest way to create a reference to, say, /dev from a string? I came up with "FSFilesystem disk root resolveString: '/dev'." Anything better? Also, what's the difference between FSReference>> resolve: resolveString: ? They both seem to do the same thing in this case. Thanks. Sean -- View this message in context: http://forum.world.st/Creating-a-FSReference-tp3962401p3962401.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 1, 2011

Exception style

by Jeff Gray

I have just watched James Robertson's Exception screencast on exceptions in Pharo. I haven't really bothered with it previously as I have only played around and haven't done anything in anger. My commercial background in Java and C# has been with quite different styles of exception handling. Java was always cluttered with exception handling and re-throwing all through the code whereas in .net it was very much a 'let it bubble up to the container' approach. Although James screencast shows the mechanics of exceptions I'm wondering what is a normal exception handling strategy in Pharo? Obvoiusly tutorial code doesn't want to get bogged down with exceptions when trying to teach a specific aspect in smalltalk/pharo/oo etc but I'm yet to see tutorial example code that handles exceptions. -- View this message in context: http://forum.world.st/Exception-style-tp3962162p3962162.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 1, 2011