April 2015 - Esug-list - lists.esug.org

ESUG 2015 Early registration is 1st of June

by Stéphane Ducasse

Hi Smalltalkers pay attention ESUG 2015 Early registration is 1st of June http://www.esug.org/wiki/pier/Conferences/2015/Conference-Registration Stef -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

April 24, 2015

Fwd: The April Edition of the Cincom Smalltalk™ Digest

by Stéphane Ducasse

See you at Brescia :) Begin forwarded message: > From: Cincom Smalltalk Product Team <jjordan(a)cincom.com> > Subject: The April Edition of the Cincom Smalltalk™ Digest > Date: 23 Apr 2015 22:04:07 GMT+3 > To: stephane.ducasse(a)inria.fr > Reply-To: jjordan(a)cincom.com > > Not rendering correctly? View this email as a web page here. > > > Cincom Smalltalk™ Digest April 2015 Edition > > Product News > Product Upgrade — Cincom® ObjectStudio® 8.6.1 and Cincom® VisualWorks® 8.0.1 Now Available to Cincom Smalltalk Customers and Partners! > Product Availability — The Current Personal Use License Versions are Cincom ObjectStudio 8.6 and Cincom VisualWorks 8.0 > Meeting the Demand Challenge — Cincom Smalltalk's Answer to the Web App Development Demand > A Shared Cornerstone — The Cincom Smalltalk Foundation > New and Improved Capabilities — Cincom Smalltalk Foundation Series: Text 2 > Helpful Technical Information — Map/Reduce, Hadoop and Cincom Smalltalk > Simple, Convenient Text Creation — A Transcript Alternative > Performance Considerations — Concurrency and Leveraging Multi-Core PCs: The Solution? MatriX > Task Simplification — Are You Looking to Boost Application Performance? > Common Tools Tutorials — "Common Tools" Tutorial Videos Available > Product Information Tutorials — Product Information Tutorials Available > Product Update — Major Update of Roassal > Smalltalk Achievements > Smalltalk the Winner! — Smalltalk Comes Out on Top in Recent Language Productivity Paper > News and Upcoming Event > April 25-26, 2015 —CampSmalltalk Spring Edition(Vancouver Island, British Columbia, Canada) > June 12-14, 2015 — Camp Smalltalk Ottawa (Ottawa, Canada) > July 15, 2015 — International Workshop on Smalltalk Technologies (IWST15) (Brescia, Italy) > July 13-17, 2015 — The 23rd International Smalltalk Joint Conference (Brescia, Italy) > Also, please note that registration for the conference is now open, and it's the last call for those who would like to be a student volunteer. > The 2016 Canadian Smalltalk Competition > Update on Smalltalk Events > Smalltalk News Repositories > News from the Team > Smalltalk Reflections Podcast > Cincom Smalltalk Community Blogs > Resources > Partner Program > Event Promotion > Contributed Components > User Portal > Social Media Channels > Online Product Information > Academic Program > > > Cherniak Software > > “What had attracted the Cherniak team to Smalltalk were the promised 'huge productivity gains,'" said founder Bob Cherniak. “So our main reasons were what it could do to help us develop quality, robust applications quickly.” > > — Bob Cherniak, > Founder, Cherniak Software > > To see more stories, click here. > Smalltalk Job Opportunities > Cincom Smalltalk Team Seeks VisualWorks Software Engineers > Visit the Smalltalk Jobs Blog > > > > > > Cincom Systems 55 Merchant Street Cincinnati, OH 45246 USA > Cincom, the Quadrant Logo, Cincom Smalltalk, ObjectStudio and VisualWorks are trademarks or registered trademarks of Cincom Systems, Inc. > All other trademarks belong to their respective companies. > ©2015 Cincom Systems, Inc. All Rights Reserved > > You received this email because you are subscribed to Marketing Information from Cincom Systems. > > Update your email preferences to choose the types of emails you receive. > > Unsubscribe from all future emails > -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

April 24, 2015

Internship around Smalltalk

by Stéphane Ducasse

Proposition de stage en informatique – Conception d’un éditeur de diagramme de classes UML pour l’implémentation de modèles multi-agents - Dans le cadre du développement de sa plateforme de modélisation et simulation multi-agent, Cormas (http://cormas.cirad.fr) l’Unité de Recherche GREEN du Cirad (http://ur-green.cirad.fr) propose un stage indemnisé de 6 mois pour un étudiant en informatique pour développer un module de Cormas . Ce développement informatique consiste à mettre au point un éditeur graphique permettant de dessiner un diagramme de classes UML et de générer du code SmallTalk (à la fois en VisualWorks de Cincom et en Pharo, open-source) de la structure du modèle en se référant au standard "Executable UML" (xUML) proposé par Mellor & Balcer (2002) and adopté par l’OMG (2003). Pour ce travail, nous ne cherchons pas un éditeur exhaustif intégrant tous les éléments décrits par UML2. Pour cet éditeur, les éléments du méta-modèle proposés seront limités à : la classe, ses attributs et ses méthodes, la spécialisation de classes et les associations. Les associations sont simples (uniquement binaires) et sont définies par leur nom et par leurs extrémités qui comportent chacune un nom de rôle, une valeur de multiplicité et la navigabilité. Cormas étant un framework, le modèle créé par un utilisateur doit s’ancrer sur des classes prédéfinies disponibles dans Cormas. A la fin de la conception de son modèle, l’utilisateur devra être invité à rattacher les classes qu’il a créées aux classes prédéfinies. Dans ce cas, les propriétés héritées (méthodes, associations, attributs, ...) devront être spécifiées dans le diagramme conceptuel de l’utilisateur qui pourra être affiché de façon indépendante du framework. Outre la création dynamique du squelette des classes, le stagiaire devra porter une attention particulière aux associations entre classes uni ou bi-directionnelles qui seront traduites en attributs nommés selon le rôle de l’extrémité de l’association (on parle parfois de d’association dégénérée pour laquelle le rôle de l’extrémité opposée est traduit en attribut). Ne seront pas prises en compte les classes-associations, ni les associations n-aires, ni les associations qualifiées. Cet éditeur permettra également de ré-afficher un modèle déjà sauvegarder mais aussi de proposer de générer un nouveau diagramme à partir d’un modèle déjà implémenté (rétro-ingénierie). Par ailleurs, un éditeur de diagramme d’activité xUML est déjà disponible dans Cormas. En sélectionnant une méthode de son diagramme de classes, l’utilisateur pourra alors dessiner le comportement de cette méthode en décrivant la succession des activités et des conditions booléennes. Bien que la distribution de VisualWorks s’accompagne de quelques outils permettant des aller-retours entre du code Smalltalk et des diagrammes UML (ADvance, Gipa, BOOST, MetaEdit+, DoME, UMLForSmalltalk ou Umbrello,...), le développement de l’éditeur UML devra se faire sous Roassal. En effet, avec la sortie récente de Roassal2, un moteur puissant de visualisation (http://objectprofile.com/Roassal.html) disponible à la fois pour VisualWorks et pour Pharo, la mise au point de ce module UML permettra d’accélérer la migration de Cormas sous Pharo. En option, il sera intéressant de pouvoir générer le code XML (XMI) d’un modèle pour pouvoir le lire dans un autre éditeur. ______ Durée : 6 mois (ou moins si nécessaire) Gratification : 485,10 € par mois. Lieu : pas d’accueil prévu au Cirad. L’étudiant travaillera dans son laboratoire mais des contacts réguliers seront proposés. Contacts : Pierre Bommel (bommel(a)cirad.fr) et Grégoire Leclerc (Leclerc(a)cirad.fr) [PB1] Profil de candidature : Etudiant en Informatique, License ou Master, ayant un goût pour la modélisation et la simulation. L’étudiant doit avoir de bonnes connaissances des concepts de la modélisation objet et d’UML. Des compétences en programmation Smalltalk devront être acquises. Bommel, P., Dieguez, F., Bartaburu, D., Duarte, E., Montes, E., Pereira, M., Corral, J., Lucena, C. de and Morales Grosskopf, H. (2014). A Further Step Towards Participatory Modelling. Fostering Stakeholder Involvement in Designing Models by Using Executable UML. Journal of Artificial Societies and Social Simulation 17 (1) 6 <http://jasss.soc.surrey.ac.uk/17/1/6.html>. Mellor, S. J., & Balcer, M. J. (2002). Executable UML : a foundation for model-driven architecture. Boston; San Francisco; New York: Addison-Wesley. -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

April 23, 2015

Re: [Esug-list] [Pharo-users] [ANN] Pharo 4.0 is released!

by volkert

Coooool! Yes, spread the Word. Is there a cool promotion flyer / booklet for Pharo? I found this here: http://files.pharo.org/media/flyer-cheat-sheet.pdf. Not really attractive ... Is there something better? BW, Volkert Am 16.04.2015 um 11:29 schrieb Esteban Lorenzano: > Please spread widely. > Sorry for multiple posts. >

April 18, 2015

[ESUG'15] Last call for student volunteers

by Damien Cassou

Hi, you are a student? You want to attend a nice conference but don't have money to afford it? Please apply to the student volunteer program: http://www.esug.org/Conferences/2015/Student-volunteers This is the last call. Best, -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 17, 2015

[ANN] ESUG'15 registration is open

by Luc Fabresse

Dear Smalltalkers, I am pleased to announce that registration for the 23rd ESUG Conference in Brescia, Italy is now open! To register, please proceed to the website http://www.esug.org/wiki/pier/Conferences/2015 or go directly to http://registration.esug.org Note: Fill carefully your registration because you will receive an automatically generated invoice by email. Important: do not forget to book your accommodation directly at one of the hotels in Brescia. See: http://www.esug.org/wiki/pier/Conferences/2015/Hotels See you all @ Brescia, Best, Luc Fabresse On behalf of the ESUG board and ESUG'15 local organizers PS: Please forward widely

April 17, 2015

Re: [Esug-list] [ANN] Pharo 4.0 is released!

by stephane ducasse

Thanks. We have so much ideas of where we want to go :) Stay tuned. Stef On 16 Apr 2015, at 23:07, Graham McLeod <mcleod(a)iafrica.com> wrote: > Hi Esteban, Stef, Marcus... and ALL contributors > > Just a note from those who for various reasons cannot be part of the great core team.. > > Great work and we really do appreciate both the direction in which the product is moving and the > hard work and passion which you all put into it. > > Thanks! > > Graham > >> Esteban Lorenzano 16 April 2015 at 11:29 >> Please spread widely. >> Sorry for multiple posts. >> >> (this post can be see >> here: http://pharo.org/news/pharo-4.0-released) >> >> Dear World, >> >> Pharo 4.0 (http://www.pharo.org) >> is here. >> >> Pharo is a pure >> object-oriented programming language and a powerful environment, focused >> on simplicity and immediate feedback. >> >> >> Many things have changed in Pharo. >> Here are some highlights: >> - Inspector/Playground/Spotter are new moldable >> development tools for inspecting, coding and searching objects. >> - Slots model instance >> variables as first class entities and enable meta-programming on this >> level. >> - >> ShoreLine reporter introduces a way to report system errors and collect >> statistics, that we will use for future improvements >> - Dark theme. >> >> These are just the >> more prominent highlights, but the details are just as important. We >> have closed 1697 issues in Pharo 4. Take a moment to go through a more >> detailed recount of the progress: >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md >> >> Pharo is >> improving on many fronts, but one of the most prominent changes is the >> addition of moldable tools for inspection and search. These tools >> provide extension mechanisms that allow every object to define ways in >> which it can be understood effectively. To provide an idea of the impact >> of the already existing extensions, the map below shows the Pharo >> classes grouped in packages, highlighting in red those parts of the >> system that have at least one such custom view coming with the main >> distribution. The spread of these extensions shows that moldability is >> powerful mechanism that can be used in many contexts. >> >> >> >> Remember that Pharo is your platform. >> We thank all the contributors of this release: >> >> Clara Allende, >> Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, >> Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, >> Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien >> Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, >> Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, >> Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane >> Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire >> Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, >> Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, >> Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, >> Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim >> Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, >> Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien >> Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio >> Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, >> Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter >> Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, >> Martin Walk, Richard Wettel, Dmitri Zagidulin >> >> And all those who >> contributed indirectly, by reporting bugs, participating in discussion >> threads, providing feedback... >> >> Pharo 4.0 is another big step. And, >> the best is yet to come. >> >> Enjoy! >> The Pharo Team >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > <mcleod.vcf>_______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

April 17, 2015

Re: [Esug-list] ESUG Registration?

by Luc Fabresse

Hi James, It will be open very soon. Best, #Luc 2015-04-16 23:23 GMT+02:00 James Foster <Smalltalk(a)jgfoster.net>: > Any word on when we will be able to register for ESUG? > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >

April 17, 2015

ESUG Registration?

by James Foster

Any word on when we will be able to register for ESUG?

April 16, 2015

Re: [Esug-list] [ANN] Pharo 4.0 is released!

by Graham McLeod

Hi Esteban, Stef, Marcus... and ALL contributors Just a note from those who for various reasons cannot be part of the great core team.. Great work and we really do appreciate both the direction in which the product is moving and the hard work and passion which you all put into it. Thanks! Graham > Esteban Lorenzano <mailto:estebanlm@gmail.com> > 16 April 2015 at 11:29 > Please spread widely. > Sorry for multiple posts. > > (this post can be see here: http://pharo.org/news/pharo-4.0-released) > > Dear World, > > Pharo 4.0 (http://www.pharo.org) is here. > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > Many things have changed in Pharo. Here are some highlights: > - Inspector/Playground/Spotter are new moldable development tools for > inspecting, coding and searching objects. > - Slots model instance variables as first class entities and enable > meta-programming on this level. > - ShoreLine reporter introduces a way to report system errors and > collect statistics, that we will use for future improvements > - Dark theme. > > These are just the more prominent highlights, but the details are just > as important. We have closed 1697 issues in Pharo 4. Take a moment to > go through a more detailed recount of the progress: > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > > Pharo is improving on many fronts, but one of the most prominent > changes is the addition of moldable tools for inspection and search. > These tools provide extension mechanisms that allow every object to > define ways in which it can be understood effectively. To provide an > idea of the impact of the already existing extensions, the map below > shows the Pharo classes grouped in packages, highlighting in red those > parts of the system that have at least one such custom view coming > with the main distribution. The spread of these extensions shows that > moldability is powerful mechanism that can be used in many contexts. > > > Remember that Pharo is your platform. We thank all the contributors of > this release: > > Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe > Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent > Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven > Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, > Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso > Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus > Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc > Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, > Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale > Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, > Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, > David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, > Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan > Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik > Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, > Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres > Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin > Walk, Richard Wettel, Dmitri Zagidulin > > And all those who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > > Pharo 4.0 is another big step. And, the best is yet to come. > > Enjoy! > The Pharo Team > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

April 16, 2015

Re: [Esug-list] [Pharo-users] [ANN] Pharo 4.0 is released!

by Mariano Martinez Peck

Super good news! thank you all! On Thu, Apr 16, 2015 at 1:08 PM, Richard Wettel <wettel(a)gmail.com> wrote: > Great! And thank you all! > Ricky > > — > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > On Thu, Apr 16, 2015 at 5:24 PM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> Thank you all ! >> >> On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> Please spread widely. >>> Sorry for multiple posts. >>> >>> (this post can be see here: http://pharo.org/news/pharo-4.0-released) >>> >>> Dear World, >>> >>> Pharo 4.0 (http://www.pharo.org) is here. >>> >>> Pharo is a pure object-oriented programming language and a powerful >>> environment, focused on simplicity and immediate feedback. >>> >>> Many things have changed in Pharo. Here are some highlights: >>> - Inspector/Playground/Spotter are new moldable development tools for >>> inspecting, coding and searching objects. >>> - Slots model instance variables as first class entities and enable >>> meta-programming on this level. >>> - ShoreLine reporter introduces a way to report system errors and >>> collect statistics, that we will use for future improvements >>> - Dark theme. >>> >>> These are just the more prominent highlights, but the details are just >>> as important. We have closed 1697 issues in Pharo 4. Take a moment to go >>> through a more detailed recount of the progress: >>> >>> >>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md >>> >>> Pharo is improving on many fronts, but one of the most prominent changes >>> is the addition of moldable tools for inspection and search. These tools >>> provide extension mechanisms that allow every object to define ways in >>> which it can be understood effectively. To provide an idea of the impact of >>> the already existing extensions, the map below shows the Pharo classes >>> grouped in packages, highlighting in red those parts of the system that >>> have at least one such custom view coming with the main distribution. The >>> spread of these extensions shows that moldability is powerful mechanism >>> that can be used in many contexts. >>> >>> >>> Remember that Pharo is your platform. We thank all the contributors of >>> this release: >>> >>> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe >>> Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, >>> Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, >>> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei >>> Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, >>> Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane >>> Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, >>> Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, >>> Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, >>> Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max >>> Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila >>> Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot >>> Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, >>> Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, >>> Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian >>> Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, >>> Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin >>> >>> And all those who contributed indirectly, by reporting bugs, >>> participating in discussion threads, providing feedback... >>> >>> Pharo 4.0 is another big step. And, the best is yet to come. >>> >>> Enjoy! >>> The Pharo Team >>> >>> >>> _______________________________________________ >>> Esug-list mailing list >>> Esug-list(a)lists.esug.org >>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >>> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> > > -- Mariano http://marianopeck.wordpress.com

April 16, 2015

Re: [Esug-list] [ANN] Pharo 4.0 is released!

by Serge Stinckwich

Thank you all ! On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Please spread widely. > Sorry for multiple posts. > > (this post can be see here: http://pharo.org/news/pharo-4.0-released) > > Dear World, > > Pharo 4.0 (http://www.pharo.org) is here. > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > Many things have changed in Pharo. Here are some highlights: > - Inspector/Playground/Spotter are new moldable development tools for > inspecting, coding and searching objects. > - Slots model instance variables as first class entities and enable > meta-programming on this level. > - ShoreLine reporter introduces a way to report system errors and collect > statistics, that we will use for future improvements > - Dark theme. > > These are just the more prominent highlights, but the details are just as > important. We have closed 1697 issues in Pharo 4. Take a moment to go > through a more detailed recount of the progress: > > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > > Pharo is improving on many fronts, but one of the most prominent changes > is the addition of moldable tools for inspection and search. These tools > provide extension mechanisms that allow every object to define ways in > which it can be understood effectively. To provide an idea of the impact of > the already existing extensions, the map below shows the Pharo classes > grouped in packages, highlighting in red those parts of the system that > have at least one such custom view coming with the main distribution. The > spread of these extensions shows that moldability is powerful mechanism > that can be used in many contexts. > > > Remember that Pharo is your platform. We thank all the contributors of > this release: > > Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, > Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury > Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei > Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, > Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane > Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, > Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, > Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, > Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max > Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot > Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, > Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, > Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian > Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, > Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin > > And all those who contributed indirectly, by reporting bugs, participating > in discussion threads, providing feedback... > > Pharo 4.0 is another big step. And, the best is yet to come. > > Enjoy! > The Pharo Team > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 16, 2015

Re: [Esug-list] [ANN] Pharo 4.0 is released!

by Esteban Lorenzano

spreading the word: https://news.ycombinator.com/item?id=9386775 <https://news.ycombinator.com/item?id=9386775> http://www.reddit.com/r/programming/comments/32sdli/pharo_40_the_immersive_… <http://www.reddit.com/r/programming/comments/32sdli/pharo_40_the_immersive_…> cheers, Esteban > On 16 Apr 2015, at 11:29, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Please spread widely. >

April 16, 2015

[ANN] Pharo 4.0 is released!

by Esteban Lorenzano

Please spread widely. Sorry for multiple posts. (this post can be see here: http://pharo.org/news/pharo-4.0-released <http://pharo.org/news/pharo-4.0-released>) Dear World, Pharo 4.0 (http://www.pharo.org) is here. Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Many things have changed in Pharo. Here are some highlights: - Inspector/Playground/Spotter are new moldable development tools for inspecting, coding and searching objects. - Slots model instance variables as first class entities and enable meta-programming on this level. - ShoreLine reporter introduces a way to report system errors and collect statistics, that we will use for future improvements - Dark theme. These are just the more prominent highlights, but the details are just as important. We have closed 1697 issues in Pharo 4. Take a moment to go through a more detailed recount of the progress: https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md Pharo is improving on many fronts, but one of the most prominent changes is the addition of moldable tools for inspection and search. These tools provide extension mechanisms that allow every object to define ways in which it can be understood effectively. To provide an idea of the impact of the already existing extensions, the map below shows the Pharo classes grouped in packages, highlighting in red those parts of the system that have at least one such custom view coming with the main distribution. The spread of these extensions shows that moldability is powerful mechanism that can be used in many contexts. Remember that Pharo is your platform. We thank all the contributors of this release: Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin And all those who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... Pharo 4.0 is another big step. And, the best is yet to come. Enjoy! The Pharo Team

April 16, 2015

23rd International Smalltalk Joint Conference - Call for Contributions

by Stéphane Ducasse

Please distribute widely 23rd International Smalltalk Joint Conference - Call for Contributions Brescia, Italy from 13 to 17 July 2015 http://www.esug.org/Conferences/2015/ This call includes: Developer Forum Smalltalk Technology Award International Workshop http://www.esug.org/wiki/pier/Conferences/2015/International-Workshop-IWST_… Student Volunteer http://www.esug.org/wiki/pier/Conferences/2015/Student-volunteers Camp Smalltalk 12 July 2015 ---------------------------------------------------------------------- You can support the ESUG conference in many different ways: * Sponsor the conference. New sponsoring packages are described at http://www.esug.org/wiki/pier/About/BecomeSponsor * Submit a talk, a software or a paper to one of the events. See below. * Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! * Students can get free registration and hosting if they enrol into the the Student Volunteers program. See below. Developers Forum: International Smalltalk Developers Conference ------------------------------------------------------------------------ We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45-60 min for hand-ons tutorial. The list of topics for the normal talks and tutorials includes, but is not limited to the following: * XP practices, Development tools, Experience reports * Model driven development, Web development, Team management * Meta-Modeling, Security, New libraries & frameworks * Educational material, Embedded systems and robotics * SOA and Web services, Interaction with other programming languages Teaching Pearls and Show us Your Business ----------------------------------------- - Show your business 10 min session (Get prepared!!) - Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. !! How to submit? -------------- Submissions deadline is 15 of May 2015 Notification of acceptance will be on done on the fly. More information at http://www.esug.org/conferences/2015 Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to Stephane.Ducasse at inria.fr AND USE THE following header [ESUG 2015 Developers]. Please follow the template below the email will be automatically processed! Subject: [ESUG 2015 Developers] + your name First Name: Last Name: Email where you can always be reached: Title: Type: Tutorial/Talk/Teaching Pearl Abstract: Bio: Any presentation not respecting this form will be discarded automatically International Workshop on Smalltalk Technologies ------------------------------------------------------------------------ Read the page: http://www.esug.org/wiki/pier/Conferences/2015/International-Workshop-IWST_… Technology Award Competition ------------------------------------------------------------------------ The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/conferences/2015/ Student Volunteer Program ------------------------------------------------------------------------ If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at http://www.esug.org/wiki/pier/Conferences/2015/ http://www.esug.org/wiki/pier/Conferences/2015/Student-volunteers We hope to see you there and have fun together. _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

April 11, 2015

CFP IWST 2015 - Deadline extension - 17th April

by jannik laval

Please note that the deadline has been extended to the 17th April 2015 . [Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST15 — International Workshop on Smalltalk Technologies Brescia, Italy; July 15, 2015 http://www.esug.org/wiki/pier/Conferences/2015/International-Workshop-IWST_… ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: Short position papers describing emerging ideas Long research papers with deeper description of experiments and of research results. Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. -------------------- Important Dates -------------------- *Submission deadline: April 17th, 2015* Notification deadline: May 20th, 2015 Workshop : July 15th, 2015 All accepted papers will be published in ACM DL ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: -Aspect-oriented programming, -Design patterns, -Experience reports, -Frameworks, -Implementation, new dialects or languages implemented in Smalltalk, -Interaction with other languages, -Meta-programming and Meta-modeling, -Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be eligible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst2015 ------------------- Program chairs ------------------- Anne Etien (Université de Lille 1, France) Jannik Laval (Ecole des Mines de Douai, France) -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info http://car.mines-douai.fr/

April 9, 2015

ESUG call for sponsors

by Luc Fabresse

Dear Smalltalkers, The European Smalltalk User Group (ESUG) welcome sponsors for the organization of the 23rd ESUG conference edition ( http://www.esug.org/wiki/pier/Conferences/2015) Sponsoring ESUG also help us to do achieve multiple actions to support Smalltalk all over the year such as: conferences, events, summertalks, projects, research articles, publications, books, student mobility, ... More infos at: http://www.esug.org/wiki/pier/Promotion. As previous years (http://www.esug.org/About/BecomeSponsor) sponsorships level are: * Silver ESUG Sponsor: By paying 500€, the logo of your company/association is displayed during the ESUG conference, and you are also recognized as a sponsor on our ESUG website http://www.esug.org. You are entitled to mention that you are an ESUG sponsor, and to use the ESUG logo in that context. * Gold ESUG Sponsor: By paying 1000€, you get all of the above, and ESUG correspondence and distributions (CD, Documentation) will feature your logo. You also get a 10% fee reduction on the ESUG events for up to 5 people of your organization. * Platinum ESUG Sponsor: By Paying 2000€, you get all of the above, but you get a 20% fee reduction on the ESUG events for up to 10 people of your organization. If your company is interested, you can choose a sponsorship level, send us (at board(a)esug.org) information such as Organization name, VAT number, etc. and we will send you back an invoice. Also consider that sending people to the conference is a kind of sponsoring in an indirect way. So see you @ ESUG'15, Brescia, Italy 13-17 July 2015. Best regards, Luc Fabresse On behalf of ESUG board PS: Forward widely #Luc

April 4, 2015

Re: [Esug-list] Nested Degenerate Convenience Methods

by Steven Kelly

I'd say it's similar to currying, but not actual currying. 1) In this Smalltalk pattern, the extra default argument is fixed, provided at compile time; with currying, the extra argument is provided at runtime. 2) In Smalltalk, the result of any of the methods is the actual return value, whereas in currying it's a function until the last case. This is more like partial function application: http://en.wikipedia.org/wiki/Currying#Contrast_with_partial_function_applic… ion but that only solves 2), not 1). Blocks can go all the way. I'm not a functional programming expert, though! Steve Andres Valloud wrote April 2, 2015 11:38 AM: > ... /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 > >> > >> > > > > _______________________________________________ > 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 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