June 2014 - Pharo-dev - lists.pharo.org

ConfigurationOfZincHTTPComponents class>>#catalogKeywords - can we change that a little bit?

by Paul DeBruicker

The current method is #catalogKeywords ^ #(#networking #internet #http #client #server #request #response #url #mime-type #character-encoding) Can we change it to #catalogKeywords ^ #(#networking #internet #http #client #server #request #response #url #mimeType #characterEncoding) So the GemStone parser can handle it? Thanks Paul

June 10, 2014

PharoWebDoc

by phil＠highoctane.be

Is there any place where one can reliably load PharoWebDoc parts? I see things in the configuration browser (PPMarkdown) But this gives issues in 3.0 Then github from Camillo and Esteban (a fork). And in the configurations themselves it looks like a mess. I cloned the repos and tried to load with filetree:// (and I do have a working gitfiletree://). But it still complains while I try to load WebDoc.package (about PPToken). The package I am trying to load is WebDoc.package Name: WebDoc-EstebanLorenzano.160 Author: EstebanLorenzano Time: 15 May 2014, 1:51:15.208571 pm UUID: 3e9d23ed-98e7-4095-bc83-94c16987f1d8 Ancestors: WebDoc-EstebanLorenzano.159 empty log message TIA Phil

June 10, 2014

CFP - IWST 2014 - Deadline Extension - June, 22

by jannik laval

Dear smalltalkers, we decided to extend the deadline for submitting contributions to IWST. The new deadline is set to *22nd June, 2014*. ************************************************************ ************************************************ [Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST14 â International Workshop on Smalltalk Technologies Cambridge, England; August 19, 2014 http://www.esug.org/Conferences/2014/IWST14 ************************************************************************************************************ ------------------- 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: June 15, 2014 Notification deadline: July 15, 2014 Workshop : August 19, 2014 All accepted papers will be published in ACM DL (To be confirmed) ------------------- 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 Lam Research Corporation for its financial contribution that makes it possible a price 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 illegible, 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://www.easychair.org/conferences/?conf=iwst2014 ------------------- Program chairs ------------------- Alain Plantec (UMR 6265 Lab-STICC, University of Brest, 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://car.mines-douai.fr/

June 10, 2014

[website] Small updates to Documentation page

by Marcus Denker

http://pharo.org/documentation - added talk of Doru to the presentations. - added Pharo for the Enterprise to the book section. Marcus

June 10, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40019 Home: https://github.com/pharo-project/pharo-core

June 10, 2014

[pharo-project/pharo-core] 07213e: 40019

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 07213e6d7a3dcaf44387a7f38d71c1011321f4cd https://github.com/pharo-project/pharo-core/commit/07213e6d7a3dcaf44387a7f3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-10 (Tue, 10 Jun 2014) Changed paths: R Network-MIME.package/Base64MimeConverter.class/class/as yet unclassified/decodeInteger_.st R Network-MIME.package/Base64MimeConverter.class/class/as yet unclassified/encodeInteger_.st R Network-MIME.package/Base64MimeConverter.class/class/as yet unclassified/mimeDecodeToBytes_.st R Network-MIME.package/Base64MimeConverter.class/class/as yet unclassified/mimeDecodeToChars_.st R Network-MIME.package/Base64MimeConverter.class/class/as yet unclassified/mimeEncode_multiLine_.st R Network-MIME.package/Base64MimeConverter.class/class/convenience/mimeEncode_.st A Network-MIME.package/Base64MimeConverter.class/class/encoding/decodeInteger_.st A Network-MIME.package/Base64MimeConverter.class/class/encoding/encodeInteger_.st A Network-MIME.package/Base64MimeConverter.class/class/encoding/mimeDecodeToBytes_.st A Network-MIME.package/Base64MimeConverter.class/class/encoding/mimeDecodeToChars_.st A Network-MIME.package/Base64MimeConverter.class/class/encoding/mimeEncode_.st A Network-MIME.package/Base64MimeConverter.class/class/encoding/mimeEncode_multiLine_.st R SUnit-Core.package/UITestCase.class/README.md R SUnit-Core.package/UITestCase.class/definition.st R SUnit-Core.package/UITestCase.class/instance/running/runCase.st A SUnit-UITesting.package/UITestCase.class/README.md A SUnit-UITesting.package/UITestCase.class/definition.st A SUnit-UITesting.package/UITestCase.class/instance/running/runCase.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script19.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40019.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40019 13319 Small recategorization in Network-MIME to test money https://pharo.fogbugz.com/f/cases/13319 13262 UITestCase in wrong package https://pharo.fogbugz.com/f/cases/13262 http://files.pharo.org/image/40/40019.zip

June 10, 2014

Re: [Pharo-dev] Windows VM question

by Hilaire Fernandes

Of course I meant I want to move those .dll files in a subdirectory. Thanks Hilaire Le 10/06/2014 17:55, Hilaire Fernandes a Ã©crit : > Now I would like to hide all this *.dll files. I check for the .ini > parameters but I did not find anything. Did I miss somethings? -- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa

June 10, 2014

Windows VM question

by Hilaire Fernandes

Hello, When I look at the Windows VM file directory, it looks like this: Contents FT2Plugin.dll libcairo-2.dll libeay32.dll libfreetype-6.dll libgit2.dll libpixman-1-0.dll libpng-3.dll libssh2-1.dll Pharo.exe SqueakFFIPrims.dll SqueakSSL.dll ssleay32.dll zlib1.dll Now I would like to hide all this *.dll files. I check for the .ini parameters but I did not find anything. Did I miss somethings? Thanks Hilaire -- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa

June 10, 2014

Re: [Pharo-dev] Pharo compilation limits

by ClÃ©ment Bera

2014-06-10 14:32 GMT+02:00 GOUBIER Thierry <thierry.goubier(a)cea.fr>: > Hi Clement, > > I'm hitting the maximum jump size limit. The method is around 10000 > characters long, with a sequence of ifTrue: ifFalse: > Hello, For now, this issue is hard to solve. The maximum length of a jump is 1024 instructions (cf bytecode table here: http://clementbera.wordpress.com/2013/09/23/squeakv3plusclosure-bytecode-se… ). The problem of computing the maximum bytecode length of a sequence form a parse tree is that each AST nodes may generate bytecodes of a variable length. In addition, control flow optimizations are done in Opal after the AST, therefore a block node may generate bytecodes of very different sizes. Lastly, we will change the bytecode set in a few months (partly to solve the issue you have) and your bytecode length assumptions will not be valid any more. I think the best way is to catch the error while compiling and override the error behavior. Right now a generic error is raised but it can be fixed. Look at: IRBytecodeGenerator>>jumpForward: , jumpBackward: , jump:if: Replace all the error signals by something like: self error: 'forward jump too big' ====>>> JumpTooBigCompilationError new info: specificInfosFromCompilerToTipSmaCCOnHowToGenerateWorkingCode; signal. Then you can catch it for your compilations. [ "compilation code" ] on: JumpTooBigCompilationError do: [ :ex | "exception handling code" ]. For example: [ Smalltalk compiler source: 'foo ^ nil'; class: Object; failBlock: [^ nil]; compile ] on: JumpTooBigCompilationError do: [ :ex | SmaCC new regenerateMethodBasedOn: ex info ]. However, this issue will be solved in Pharo 4 in a few months. The maximum number of instructions a jump can handle will be increased from 1024 to around 32000. If this is still not enough for you, tell us then we'll patch the compiler backend and the VM front end to work with more important instruction size. Clement > > Thierry > ------------------------------ > *De :* Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de > ClÃ©ment Bera [bera.clement(a)gmail.com] > *EnvoyÃ© :* mardi 10 juin 2014 08:15 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] Pharo compilation limits > > > > > 2014-06-10 2:23 GMT+02:00 GOUBIER Thierry <thierry.goubier(a)cea.fr>: > >> Hi all, >> >> anybody would have a way to determine the maximum length / maximum >> complexity of a method in a Pharo out of a parse tree (or whether if the >> parse tree is over the limit)? >> >> There are many different issues: maximum number of literals, maximum > jump size, maximum number of temporaries. Can you precise what problem do > you have ? What errors are raised ? > > >> The code SmaCC generates easily hit compiler limits (methods too long or >> too complex), and I have difficulties changing the code generation approach. >> > > For Pharo 4, we are implementing a new compiler back end that will > remove some of those limits. I have a problem with code generation too and > we are solving it. > > ClÃ©ment > >> >> Thanks, >> >> Thierry >> >> >> >

June 10, 2014

Re: [Pharo-dev] [Seaside-dev] builds for pharo 4?

by Sven Van Caekenberghe

On 10 Jun 2014, at 15:40, Philippe Marschall <philippe.marschall(a)gmail.com> wrote: > On Tue, Jun 10, 2014 at 2:50 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> The concepts âstableâ and âPharo 4â are incompatibles right now :) >> Even if now is not really divergent from Pharo 3 (and I think is working very stable), is a development versionâ¦ even worst, is not even an alpha. >> And it will be like that during some monthsâ¦ I wouldnât bet on his stability for now. > > Is there a way I don't get failure emails for Pharo 4 other than > setting up a rule in my user agent? It is very useful to have continuous Seaside builds to ensure future compatibility. But right now, because Pharo 4 is just starting its evolution, it is way too early to take the failures very seriously. Hence, sending so many mails around is too much. I would vote for keeping the CI jobs, but sending less or no notifications for those based on 4.0. Sven

June 10, 2014