March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by Eliot Miranda

On Tue, Mar 12, 2013 at 7:54 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 12 March 2013 19:44, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > > 3. Pharo has forked the VM to include a) NativeBoost and b) ephemerons > and > > c) new FileSystem primitives. > > a) is cool, but I don't like the x86 specificity. I want a > cross-platform > > FFI, so I'm not excited enough to include NB in my port. > > Just let me remind you that (x86 specificity) is completely on image side. > The VM side changes are minimal and 100% not platform specific. > Making NB image-side implementation platform-unspecific is another story.. > but as i said before i see no reason to do it unless there's a version > of Cog which runs > on some other platform :) > I understand that. I think Squeak should provide a platform-independent FFI at the image level. > > There is plans and some work started on getting there, by making a > platform-neutral low-level > DSL, which can be used for generating native code. > This is called RTL ;) > > -- > Best regards, > Igor Stasenko. > > -- best, Eliot

March 13, 2013

Re: [Pharo-project] [Moose-dev] Re: where to report vm crashes? (while running Moose tests)

by Esteban Lorenzano

Hi, Doru, I just compiled a new version of the VM, that mixes a merge from latest Eliot sources with a lot of work in the optimization flags to prevent random crashes (yes, I hate C and its nondeterministic behavior for VMs :P). Moose tests are now not crashing in my machine (both in mac and unix... didn't tested in windows). Can you check if this solves the problem? https://ci.inria.fr/pharo/view/VM/job/PharoVM/Architecture=32,Slave=vm-buil… https://ci.inria.fr/pharo/view/VM/job/PharoVM/Architecture=32,Slave=vm-buil… cheers, Esteban On Mar 12, 2013, at 9:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > It would be good to have a parallel job, but the problem is that you will get a message saying that the VM is too old for the Pharo 2.0 image. > > Cheers, > Doru > > > On Tue, Mar 12, 2013 at 9:05 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > Doru, > > In the meantime, can we revert to CogVM because currently we cannot see the status of fixes and we cannot go any further with Moose 4.8 or may be create parallel jobs on Cog and Pharo vms ? > > > > On Mon, Mar 11, 2013 at 9:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Where should I report Pharo VM crashes with Pharo 2.0? > > In particular, I wanted to report the problem related to running Moose tests from the command line: > > --- > You can reproduce it on Mac, quite consistently: just run the attached script (you need to have wget installed), or do it manually: > > 1. download and unzip the latest Moose 4.8: > https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/arti… > 2. download and unzip the latest Pharo VM: > http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip > 3. execute: > ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest > > The VM crashes, but there is no trace of the error. > --- > > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 13, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Igor Stasenko

On 12 March 2013 16:08, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > It is hard to remember.. but i will try: - working on VM builds, making things run.. crashing and run again - working on NB & FFI - working on Athens , M4te, NBOpenGL and other cool stuff > ### What's next, until 2013-03-24 (*): > - to dominate world, i want to update configuration of NBOpenGL, so it can work fine with updated version of NativeBoost, found in Pharo 2.0 - same applies to Athens, because its configuration also needs to be updated and some testing - a small yet important project NBFpu, to test and learn NB and Jit coexistance and see how we can squeeze even more performance from our code. The outcome is more documentation how internally jit works as well as an open road for new FFI code generator which will use inline JIT code for FFI calls instead of C primitive (primitiveNativeCall) - i want to move all VMMaker sources to git repository, to no longer deal with tons of configurations and making single commit containing all necessary bits to build VM. But this can take a while -- Best regards, Igor Stasenko.

March 13, 2013

[Pharo-project] [ANN] Amber 0.10 released!

by Nicolas Petton

After a bit more than one year we have finally put together a new release of Amber - the web developer's best friend: http://www.amber-lang.net Yeah, we know, too long time for a release cycle, but we think you will like this release! First - let's run the numbers - since the 0.9.1 release there have been over 850 commits (compared to 250 for 0.9.1). We have closed 364 issues and added 150 new unit tests bringing us to 271 in total. All classes in the kernel now have comments and there are Travis jobs to keep us all in line. Forks on github have gone up from 43 to 83 with 365 followers. Phew. And what goodies does this give us? Well, first Nicolas got carried away with compiler technology (must have read a book or something) and added a whole new Super Duper compiler tool chain providing both an AST with annotations and an Intermediate Representation layer (IR) enabling semantic analysis and easier optimizations, a better inlining mechanism, support for block contexts (whoa!) and an AST interpreter to round it off. Wait a minute, what? An interpreter? Why on earth would we want a... oh. To be able to implement a full stepping debugger of course (coming in 1.0). Baddabing! Just the new compiler tool chain would have been enough for a release, but since Nicolas is not the only Elf in Amber land this release also includes SUnit improvements and cleanup with support for async assertions, a new build system based on gruntjs replacing the old makefiles (seems slicker in the land of JS), an improved ClassBuilder with better class migration support and a new amberc compiler written in Amber instead of that ghastly bash script... (deep breath) ...and an improved loader to be able to use 3rd party packages, improved kernel classes, and updated documentation. And we also split the github repo into three separate repos - Amber itself, the examples and the website - and yeah, the website got a new look. ...and a whole new IDE is brewing called Helios (in the helios branch). But nah, sorry, Helios will land in 1.0. :) We hope you join us in developing Amber and having fun! Fork at github, join in #amber-lang on freenode and hop onto the mailing list. /the Amber crew

March 13, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Stephan Eggermont

Sean wrote >- Proof-of-concept at ESUG to enhance FileTree/Cypress for VW <-> Pharo >porting, automatically converting between prefixes and namespaces; Cami and >I were able to load the newest version of Xstreams from VW, and then commit >it again in a cross platform format that could (I think, not tested) be >loaded in VW Great. Did you contact Christian Haider to try with his PDF library? That would solve one of the obstacles to getting a really good pdf library in Pharo. The other being of course the coupling to VW drawing. Stephan

March 13, 2013

Re: [Pharo-project] [Pharo-users] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

by Guillermo Polito

Hi Janko! We have this: Level: intermediate Possible mentor: Guillermo Polito Possible second mentor: Esteban Lorenzano Description: DBXTalk database driver nowadays uses a native library called OpenDBX. This library stands as an adaptor between different database drivers, implemented in C. This native library supposes many problems: - it should be normally compiled for each different platform (Windows, *nix, macosx) and database vendor - each of its bugs should be fixed in a C source code base - OpenDBX do not expose the particular behavior of each database vendor, but their common denominator - difficulty for distribution, and problems to locate libraries. This project proposes to use NativeBoost bindings to remove the necessity of the native openDBX library, simplifying the deployment of applications using relational databases, and moving all the code base to Smalltalk. Technical Details: This project supposes the replacement of openDBX old FFI bindings by direct nativeBoost bindings to the database drivers. The new drivers should be completely written in Smalltalk, and take care of platform and library resolution in the image side. These drivers should be polymorphic while also enabling the access to specific API provided by database vendors. Benefits to the Student - Use a highly reflective dynamic language - Learn the basics of foreign function interface (and its exponent NativeBoost) - Learn how to manage external resources and platform specific native code - Put into usage its object design skills to transform a structured designed library into an object oriented one Benefits to the Community - A more malleable and full smalltalk implementation of relational database drivers - Easier deploy for applications using relational databases - Database divers exposing their particular apis, providing access to features not available before Guille On Sat, Mar 9, 2013 at 2:16 PM, Janko MivÅ¡ek <janko.mivsek(a)eranova.si>wrote: > Hi Stef, > > Post on the mailing list for each project idea by following this template: > > Level: (beginner, intermediate, advanced) > > Possible mentor: > > Possible second mentor: > > Description > > Technical Details > > Benefits to the Student > > Benefits to the Community > > Best regards > Janko > > Dne 09. 03. 2013 13:46, piÅ¡e stephane ducasse: > > Hi janko > > > > How do you want to proceed for the topics? > > I have a list of topics now where do we write them. > > > > - tool support rewrite rules > > - new generation debugger > > - new change model and session manager (with martin dias) > > - improving roassal (with alexandre bergel et vanessa pena) > > - improving eyesee (with alexandre bergel et vanessa pena) > > - support touch event > > - UIPainter (with esteban lorenzano) > > - New widgets > > > > > > Stef > > > > > >> Dear Smalltalkers, > >> > >> Time for your cool project ideas on this year Smalltalk GSoC! > >> > >> For now just express any idea you have here on the mailing list. Later > >> we will together develop it to be in complete format together with two > >> mentors needed. Deadline is end of Mart, so we have three weeks of time. > >> To see how fully developed ideas look like please look at 2012 ones at: > >> http://gsoc2012.esug.org/ideas. > >> > >> Note also that students yourselves can propose a GSoC project. So if you > >> like to be a student on this year GSoC and have a nice idea, don't be > >> shy and propose it here! The community will listen you and guide to the > >> really nicely proposed project. Last year 6 student proposed projects > >> were accepted and finished successfully! > >> > >> For the community, start looking around for students. Think about how to > >> approach the universities near by you, do you know who to contact > >> there, etc. > >> > >> We are namely preparing an application to this year Smalltalk Google > >> Summer of Code under ESUG umbrella, as last year. If accepted, Google > >> will pay few stipendiums to students on our Smalltalk projects. > >> > >> More on our special Smalltalk GSoC 2013 website: > >> > >> http://gsoc2013.esug.org > >> > >> I'm specially inviting mentors of all past GSoCs to rejoin the mentors > >> mailing list, where we discuss all details about this year GSoC: > >> > >> http://groups.google.com/group/smalltalk-gsoc-mentors > >> > >> While students interested on GSoC please join a special Smalltalk GSoC > >> mailing list for you: > >> > >> http://groups.google.com/group/smalltalk-gsoc-students > >> > >> Best regards > >> Janko > >> > >> > >> -- > >> Janko MivÅ¡ek > >> Aida/Web > >> Smalltalk Web Application Server > >> http://www.aidaweb.si > >> > > > > > > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > >

March 13, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Sven Van Caekenberghe

On 12 Mar 2013, at 16:53, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - helped with the Pharo 2.0 release by testing, discussing and fixing issues - did a couple of Zinc/Zdc releases with cleanups for integration in Pharo 2.0 - delivered Zinc-SSO with Jan van de Sandt - general Zinc support as a fundamental Pharo framework - Zinc feature extensions (often by request) - switched to using Metacello configurations and the new command line features of Pharo 2.0 to build server images - cleaned up all my public code for Pharo 2.0 (NeoCSV, NeoJSON, STON, ZTimestamp) - added an SNTP client to ZTimestamp > ### What's next, until 2013-03-24 (*): - update Zinc documentation before PharoConf - extent ZnUrl>>#/ for Sean - help finalize Pharo 2.0 release - help start Pharo 3.0 - maybe do another Zinc update/sync - try to keep up with all Pharo infrastructure changes - learn from a gazillion interesting things happening in the Pharo community - continue giving support - realize some of my dreams (too much ideas, too little time) > (*) we'll be expecting results by then ;) -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

March 13, 2013

Re: [Pharo-project] Phexample official repository?

by Frank Shearar

On 13 March 2013 14:25, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi Frank: > > On 13 Mar 2013, at 12:23, Frank Shearar wrote: > >> Ah, cool. Would some kind soul update the various repositories to say >> that Phexample/Phexample is the official repository? > > I changed it. (http://smalltalkhub.com/#!/~Phexample/Phexample) > Removed the top note and added at the bottom: > > """ > Note: This is the official community-supported repository for Pharo and Squeak. The original Phexample project started on SqueakSource. > """ > > Will look into the test and a couple of other issues tonight. > > Best regards > Stefan > > PS: I also added you to the contributors. Cool, thanks Stefan. I only found out about the confusion of repositories after I sent you Phexample-fbs.64 - did it pass all tests on Pharo 1.4? If so, and you're OK with the change, I'll rebase my work off the latest version and resubmit. I'll also edit the ConfigurationOf to add a #squeak section. frank

March 13, 2013

Re: [Pharo-project] Phexample official repository?

by Stefan Marr

Hi Frank: On 13 Mar 2013, at 12:23, Frank Shearar wrote: > Ah, cool. Would some kind soul update the various repositories to say > that Phexample/Phexample is the official repository? I changed it. (http://smalltalkhub.com/#!/~Phexample/Phexample) Removed the top note and added at the bottom: """ Note: This is the official community-supported repository for Pharo and Squeak. The original Phexample project started on SqueakSource. """ Will look into the test and a couple of other issues tonight. Best regards Stefan PS: I also added you to the contributors. -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

March 13, 2013

Re: [Pharo-project] Debugger-driven development (was Re: WhatsUp from: 2013-03-11 until: 2013-03-24)

by Frank Shearar

On 13 March 2013 12:36, Stephan Eggermont <stephan(a)stack.nl> wrote: > Frank wrote: >>I'd love to hear more about your presentation. I've been thinking how >>to run a kind've live-coding demonstration at work, showing how a >>Smalltalk debugger is so clearly superior to what other folk have. > > It is inspired by Jason Ayers' session at SPA and XPDays Benelux. > It will be a short session, as there will be 2 other presentations on > non-intuitive subjects. Devnology has a diverse public with mostly > java and c# developers. Agilists in those environments are likely > to advocate writing a test instead of using a debugger, and are often > unaware of the incremental development possibilities offered by the > smalltalk debugger. > >>(Squeak trunk now lets you create methods not just on an MNU but also >>where people have things like "self subclassResponsibility", "self >>notYetImplemented" or "self shouldBeImplemented" flags such that you >>can debug-edit-and-continue.) > > Yes, I saw your blog post yesterday. Cool. That's definitely something I would > like to show. I haven't given much thought yet to which debugger I want to use. > I'm tempted to use the GTDebugger and modify it during the session > (to add your new extensions perhaps) but that is something I have to try > and time first. It might be too much magic. Huh, remarkably appropriate blog post here: http://this-plt-life.tumblr.com/post/45191922341/when-somebody-says-they-do… frank > Stephan > >

March 13, 2013