Posts in this category
- Current State of Exceptions in Rakudo and Perl 6
- Meet DBIish, a Perl 6 Database Interface
- doc.perl6.org and p6doc
- Exceptions Grant Report for May 2012
- Exceptions Grant Report -- Final update
- Perl 6 Hackathon in Oslo: Be Prepared!
- Localization for Exception Messages
- News in the Rakudo 2012.05 release
- News in the Rakudo 2012.06 release
- Perl 6 Hackathon in Oslo: Report From The First Day
- Perl 6 Hackathon in Oslo: Report From The Second Day
- Quo Vadis Perl?
- Rakudo Hack: Dynamic Export Lists
- SQLite support for DBIish
- Stop The Rewrites!
- Upcoming Perl 6 Hackathon in Oslo, Norway
- A small regex optimization for NQP and Rakudo
- Pattern Matching and Unpacking
- Rakudo's Abstract Syntax Tree
- The REPL trick
- First day at YAPC::Europe 2013 in Kiev
- YAPC Europe 2013 Day 2
- YAPC Europe 2013 Day 3
- A shiny perl6.org site
- Creating an entry point for newcomers
- An offer for software developers: free IRC logging
- Announcing try.rakudo.org, an interactive Perl 6 shell in your browser
- Another perl6.org iteration
- Blackjack and Perl 6
- Why I commit Crud to the Perl 6 Test Suite
- This Week's Contribution to Perl 6 Week 5: Implement Str.trans
- This Week's Contribution to Perl 6
- This Week's Contribution to Perl 6 Week 8: Implement $*ARGFILES for Rakudo
- This Week's Contribution to Perl 6 Week 6: Improve Book markup
- This Week's Contribution to Perl 6 Week 2: Fix up a test
- This Week's Contribution to Perl 6 Week 9: Implement Hash.pick for Rakudo
- This Week's Contribution to Perl 6 Week 11: Improve an error message for Hyper Operators
- This Week's Contribution to Perl 6 - Lottery Intermission
- This Week's Contribution to Perl 6 Week 3: Write supporting code for the MAIN sub
- This Week's Contribution to Perl 6 Week 1: A website for proto
- This Week's Contribution to Perl 6 Week 4: Implement :samecase for .subst
- This Week's Contribution to Perl 6 Week 10: Implement samespace for Rakudo
- This Week's Contribution to Perl 6 Week 7: Implement try.rakudo.org
- What is the "Cool" class in Perl 6?
- Report from the Perl 6 Hackathon in Copenhagen
- Custom operators in Rakudo
- A Perl 6 Date Module
- Defined Behaviour with Undefined Values
- Dissecting the "Starry obfu"
- The case for distributed version control systems
- Perl 6: Failing Softly with Unthrown Exceptions
- Perl 6 Compiler Feature Matrix
- The first Perl 6 module on CPAN
- A Foray into Perl 5 land
- Gabor: Keep going
- First Grant Report: Structured Error Messages
- Second Grant Report: Structured Error Messages
- Third Grant Report: Structured Error Messages
- Fourth Grant Report: Structured Error Messages
- Google Summer of Code Mentor Recap
- How core is core?
- How fast is Rakudo's "nom" branch?
- Building a Huffman Tree With Rakudo
- Immutable Sigils and Context
- Is Perl 6 really Perl?
- Mini-Challenge: Write Your Prisoner's Dilemma Strategy
- Longest Palindrome by Regex
- Perl 6: Lost in Wonderland
- Lots of momentum in the Perl 6 community
- Monetize Perl 6?
- Musings on Rakudo's spectest chart
- My first executable from Perl 6
- My first YAPC - YAPC::EU 2010 in Pisa
- Trying to implement new operators - failed
- Programming Languages Are Not Zero Sum
- Perl 6 notes from February 2011
- Notes from the YAPC::EU 2010 Rakudo hackathon
- Let's build an object
- Perl 6 is optimized for fun
- How to get a parse tree for a Perl 6 Program
- Pascal's Triangle in Perl 6
- Perl 6 in 2009
- Perl 6 in 2010
- Perl 6 in 2011 - A Retrospection
- Perl 6 ticket life cycle
- The Perl Survey and Perl 6
- The Perl 6 Advent Calendar
- Perl 6 Questions on Perlmonks
- Physical modeling with Math::Model and Perl 6
- How to Plot a Segment of a Circle with SVG
- Results from the Prisoner's Dilemma Challenge
- Protected Attributes Make No Sense
- Publicity for Perl 6
- PVC - Perl 6 Vocabulary Coach
- Fixing Rakudo Memory Leaks
- Rakudo architectural overview
- Rakudo Rocks
- Rakudo "star" announced
- My personal "I want a PONIE" wish list for Rakudo Star
- Rakudo's rough edges
- Rats and other pets
- The Real World Strikes Back - or why you shouldn't forbid stuff just because you think it's wrong
- Releasing Rakudo made easy
- Set Phasers to Stun!
- Starry Perl 6 obfu
- Recent Perl 6 Developments August 2008
- The State of Regex Modifiers in Rakudo
- Strings and Buffers
- Subroutines vs. Methods - Differences and Commonalities
- A SVG plotting adventure
- A Syntax Highlighter for Perl 6
- Test Suite Reorganization: How to move tests
- The Happiness of Design Convergence
- Thoughts on masak's Perl 6 Coding Contest
- The Three-Fold Function of the Smart Match Operator
- Perl 6 Tidings from September and October 2008
- Perl 6 Tidings for November 2008
- Perl 6 Tidings from December 2008
- Perl 6 Tidings from January 2009
- Perl 6 Tidings from February 2009
- Perl 6 Tidings from March 2009
- Perl 6 Tidings from April 2009
- Perl 6 Tidings from May 2009
- Perl 6 Tidings from May 2009 (second iteration)
- Perl 6 Tidings from June 2009
- Perl 6 Tidings from August 2009
- Perl 6 Tidings from October 2009
- Timeline for a syntax change in Perl 6
- Visualizing match trees
- Want to write shiny SVG graphics with Perl 6? Port Scruffy!
- We write a Perl 6 book for you
- When we reach 100% we did something wrong
- Where Rakudo Lives Now
- Why Rakudo needs NQP
- Why was the Perl 6 Advent Calendar such a Success?
- What you can write in Perl 6 today
- Why you don't need the Y combinator in Perl 6
- You are good enough!
Wed, 10 Mar 2010
Report from the Perl 6 Hackathon in Copenhagen
During and the "Open Source Days 2010" in Copenhagen there was a Perl 6 track, and also a hackathon that stretched out three more days after the conference.
I arrived on Saturday afternoon (which happend to be the last day of the conference) and thus missed all of the talks and the more public part of the hackathon.
On Sunday we discussed module loading extensively. Martin Berends had prepared that topic, and drove the effort by asking the right questions.
Modules are complicated beasts in Perl 6. They not only have a name and a version as in Perl 5, but they can also have so-called authorities, which handle the case when different programmers write modules with the same name. Also unlike Perl 5 a module can be installed with different versions, and the programmer can either request a particular version or the highest version available.
Also they have Unicode and case sensitive names, which Perl 6 must support even if the underlying file system does not provide both features.
Although it doesn't really sound like it, this combination of requirements make it incredibly hard to implement a module loader that is both correct and efficient. Previously all discussions on the mailing lists and IRC channels ended in huge threads full of bikeshedding and even more feature ideas.
We were well aware of these requirements before the hackathon, and also aware of the fact that we have no chance of implementing all that in a reasonable time frame. So the first step was to decide what subset of features to implement, and how that could be achieved.
We decided not to implement Unicode emulation/mapping, and partially ignore
authorities for now. Still we leave some room for wriggeling in the mapping
from module name to file name: a module
My::Module can live in
My/Module.pm or in
My/Module.ignored.pm. That way several modules with the same name
but different versions or authorities can be stored in the same module
This also implies that the Perl 6 compiler has to actually read and parse those files to find out which file to load. In a later stage the compiler will write a cache file to store the mapping from file name to module name(s), verisons, authorities, a timestamp and probably also dependencies plus timestamps (in order to know when to recompile a module).
Once this caching mechanism is implemented, it solves the Unicode problem mostly for free, because it will store the full Unicode module name and ASCII file name in the cache, and makes it available to the module locater.
After reaching an initial consensus, the discussion went on to other topics: can we use the existing CPAN infrastructure to actually distribute our modules? The conclusion was that we most likely can use (with very little patching) the PAUSE and mirroring infrastructure, but we likely have to write our own indexing and searching facilities and also a completely separate module installer.
I wrote a very simplistic prototype of a module locater in Perl 5, which Jonathan mostly translated to NQP on Monday, and actually plugged it into Rakudo's module loading facility on Tuesday.
So now you can actually have multi modules with different versions, and load the one with the highest version - requesting a particular version is not yet implemented, but hopefully now a mere SMOP.
Martin Berends wrote up the results of our module discussions, and spent the rest of his hacking time on a foreign function interface.
Not everybody worked full-time on module things; baest worked on some builtin functions and (most of the time) number handling. Carl Mäsak spent some time on tardis, his time travelling debugger. He also spent quite some effort on getting enums back into Rakudo, with occasional assistance from Jonathan.
Many of us fixed some bugs that popped up, and also found new bugs
The perl6 RT queue has grown to such a size that it was both scary and hard to use at all. On Sunday it peaked around 725 open tickets.
I did rough sweep over most of the tickets, identifying those that were either fixed (but not yet closed), superseded by changes to the specification or actually not bugs at all (spam and false reports), or could be closed by simple changes to Rakudo.
That way I closed about 80 tickets, and identified another 40 or so tickets that are actually fixed, but need test coverage before being closed.
This was the first Perlish event to which I have traveled, and it was just awesome. I met friends in "meat space" that I previously only (or mostly) knew over the Internet, and found them to be just as I had experienced them from the distance: friendly, witty, full of good jokes and bad puns, curious, relaxed and all in all a very enjoyable company.
We enjoyed the hospitality of Jonas Brømsø Nielsen and the OSD folks who did everything to make our stay pleasant: prepare the arrival with maps and tips about the public transport system, booking and funding (!) our accommodation, inviting us to lunch or dinner now and then, and being available whenever questions or problems arose. Thank you!. The March release of Rakudo will be named Copenhagen for very good reasons.
Comments / Trackbacks:
Write a comment