- Esug-list - lists.esug.org

Re: [Esug-list] Nested Degenerate Convenience Methods

by Reinout Heeck

Nested Degenerate Convenience Methods I don't have a better name, but maybe a bit of critique helps: I would say that these methods are degenerate when viewed from a bottom-up perspective. Thinking top-down we could say that some parameters are implied by the environment (self in this case) hence such methods are more abstract. I guess this might dovetail with Damiens suggestions depending on usage. Is it a pattern when it is used in a situation to hide certain concerns -- when it is used particularly to reach abstraction, to 'give' abstraction to higher layers? R - On 4/1/2015 6:49 PM, Sean P. DeNigris wrote: > Is there a name for the following pattern? > > doSomething: arg1 > ^ self doSomething: arg1 ifA: arg2Default > > doSomething: arg1 ifA: arg2 > ^ self doSomething: arg1 ifA: arg2 ifB: arg3Default > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nested-Degenerate-Convenience-Methods-tp4816719.html > Sent from the ESUG mailing list archive at Nabble.com. > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >

April 2, 2015

Re: [Esug-list] Nested Degenerate Convenience Methods

by Andres Valloud

... /me reads Wikipedia article ... It sure looks like an example of currying! On 4/1/15 22:14 , Joseph Pelrine wrote: > I agree with Andres about calling it a convenience method (and also not > calling it a pattern), but is this not also an example of currying? > > Best > Joseph > On 02.04.15 00:49, Andres Valloud wrote: >> I would call that code an example of "convenience methods". In C, those >> things would likely be implemented in terms of "macros". The term >> "pattern" is overloaded, I wouldn't use it here. >> >> On 4/1/15 9:49 , Sean P. DeNigris wrote: >>> Is there a name for the following pattern? >>> >>> doSomething: arg1 >>> ^ self doSomething: arg1 ifA: arg2Default >>> >>> doSomething: arg1 ifA: arg2 >>> ^ self doSomething: arg1 ifA: arg2 ifB: arg3Default >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/Nested-Degenerate-Convenience-Methods-tp4816719.html >>> >>> >>> Sent from the ESUG mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Esug-list mailing list >>> Esug-list(a)lists.esug.org >>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> >> >

April 2, 2015

Re: [Esug-list] Nested Degenerate Convenience Methods

by Joseph Pelrine

I agree with Andres about calling it a convenience method (and also not calling it a pattern), but is this not also an example of currying? Best Joseph On 02.04.15 00:49, Andres Valloud wrote: > I would call that code an example of "convenience methods". In C, those > things would likely be implemented in terms of "macros". The term > "pattern" is overloaded, I wouldn't use it here. > > On 4/1/15 9:49 , Sean P. DeNigris wrote: >> Is there a name for the following pattern? >> >> doSomething: arg1 >> ^ self doSomething: arg1 ifA: arg2Default >> >> doSomething: arg1 ifA: arg2 >> ^ self doSomething: arg1 ifA: arg2 ifB: arg3Default >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Nested-Degenerate-Convenience-Methods-tp4816719.html >> >> Sent from the ESUG mailing list archive at Nabble.com. >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > -- Joseph Pelrine [ | ] MetaProg GmbH Email: jpelrine(a)metaprog.com Web: http://www.metaprog.com As soon as you introduce people, things become complex.

April 2, 2015

Re: [Esug-list] Nested Degenerate Convenience Methods

by Andres Valloud

I would call that code an example of "convenience methods". In C, those things would likely be implemented in terms of "macros". The term "pattern" is overloaded, I wouldn't use it here. On 4/1/15 9:49 , Sean P. DeNigris wrote: > Is there a name for the following pattern? > > doSomething: arg1 > ^ self doSomething: arg1 ifA: arg2Default > > doSomething: arg1 ifA: arg2 > ^ self doSomething: arg1 ifA: arg2 ifB: arg3Default > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nested-Degenerate-Convenience-Methods-tp4816719.html > Sent from the ESUG mailing list archive at Nabble.com. > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >

April 1, 2015

Re: [Esug-list] Nested Degenerate Convenience Methods

by Damien Pollet

Hi Sean, I'm using "implicit default" or "implicit argument" for the chains of less and less terse methods that eventually call the fully-explicit canonic one. There is a related idiom where the explicit argument is a block, and the implicit version either results in a sentinel value or signals an exception, e.g. ifAbsent/ifNone. This one I call "default case handler". In either case, I'm not convinced the name is that clear, so if you get by a nice one, I'm interested. > On 01 Apr 2015, at 18:49, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Is there a name for the following pattern? > > doSomething: arg1 > ^ self doSomething: arg1 ifA: arg2Default > > doSomething: arg1 ifA: arg2 > ^ self doSomething: arg1 ifA: arg2 ifB: arg3Default > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nested-Degenerate-Convenience-Methods-tp4816719.html > Sent from the ESUG mailing list archive at Nabble.com. > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

April 1, 2015

Nested Degenerate Convenience Methods

by Sean P. DeNigris

Is there a name for the following pattern? doSomething: arg1 ^ self doSomething: arg1 ifA: arg2Default doSomething: arg1 ifA: arg2 ^ self doSomething: arg1 ifA: arg2 ifB: arg3Default ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nested-Degenerate-Convenience-Methods-tp4816719.html Sent from the ESUG mailing list archive at Nabble.com.

April 1, 2015

Google Code Shutdown

by Sean P. DeNigris

In case anyone hasn't heard, Google Code will shut down entirely on January 25, 2016. I was following these Smalltalk projects there: magritte-metamodel moose-technology seaside marsonpharo nativeboost metacello squeaksource3 phratch The easiest action seems to be to export to GitHub, for which Google Code even provides a button! I just used it for one of my projects and it was pretty painless. - Sean Cross-posted to ESUG, pharo-dev, squeak-dev, seaside-dev, magritte, metacello ----- Cheers, Sean -- View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814759.html Sent from the ESUG mailing list archive at Nabble.com.

March 24, 2015

Roassal and Spy

by Alexandre Bergel

Dear Community, The Smalltalk community is flourishing and the number of projects being developed is growing incredibly fast. We are happy to see an increasing number of Roassal and Spy users. Fantastic projects are being built using these frameworks. We have a very long list of todos to address many of your requests for improvement and bug fixes. Unfortunately, we have been time to time slow on addressing your request. As you can imagine, our manpower to push Roassal and Spy is limited, although it has been regularly increasing over the last three years (and will continue to do so). We would like to deliver more. Much more. Our long-term goal is to deliver the platform for visualization. Yes, we are aiming at being _the_ platform, and not simply _a_ great platform. Soon we will have D3, Protoviz, Raphael and all their friends far behind. Attaining this goal takes time. We are looking for a way to speed our effort up. That is the reason of this email. We are now making the public announcement for services provided by Object Profile, the company behind Roassal and Spy. We are selling engineering work and dedicated services. Get in touch with us for more info. Kind regards The Object Profile crew -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 19, 2015

Re: [Esug-list] Camp Smalltalk PDX

by Craig Anslow

Hi Andres and others, You could also consider doing a Smalltalk Camp at SPLASH this year in Pittsburgh. I am sure you would get a good turn out. Basically you could co-locate or submit a workshop proposal and then run the workshop/camp as you please. http://2015.splashcon.org/track/splash2015-workshops There are a number of other exciting collocated events happening as well. Thanks. Kind regards, Craig Craig Anslow, PhD Postdoctoral Research Fellow Department of Computer Science University of Calgary, Canada T: +1 587 999 8020 E: craig.anslow(a)ucalgary.ca W: http://anslow.cpsc.ucalgary.ca/ From: Andres Valloud <avalloud(a)smalltalk.comcastbiz.net<mailto:avalloud@smalltalk.comcastbiz.net>> Reply-To: <andres.valloud(a)gmail.com<mailto:andres.valloud@gmail.com>> Date: Thu, 19 Mar 2015 15:14:27 -0700 To: <esug-list(a)lists.esug.org<mailto:esug-list@lists.esug.org>> Subject: [Esug-list] Camp Smalltalk PDX A group of Smalltalkers have been discussing the possibility of having a Camp Smalltalk in Portland Oregon, August 20-23. If you think you might be interested in attending such a gathering, please let us know filling our short survey: http://goo.gl/forms/Di0rFPMcLu We also encourage you to join the SCONA mailing list here: http://scona.us/mailman/listinfo/scona-list The proposed format is: * Thursday 20th evening prior: An informal welcoming dinner at a local pub or similar. * Friday 21st morning - Sunday 23rd afternoon: The event proper, consisting of a blend of scheduled talks or discussions and free-form pair programming. * Sunday 23rd evening - Farewell dinner. The whole event is envisioned as being informal enough that showing up for only part of the time is perfectly acceptable. Your responses will help us with our planning efforts. Feel free to forward this message to any other Smalltalk forums or individual Smalltalkers you think might be interested. Andres. _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org<mailto:Esug-list@lists.esug.org> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

March 19, 2015

Camp Smalltalk PDX

by Andres Valloud

March 19, 2015