The Raku Programming Language Collect, Conserve and Remaster Project
Originally published on 25 March 2009 by Jonathan Worthington.
This is a report for my Rakudo day last week, which finished up pretty late and thus I didn’t get around to writing up and posting a report. Much of the day saw me headachey and not really feeling up to working on big stuff, so I did small stuff instead - mostly bug fixes. Those were:
prompt could be a little bit too lazy. If you call it in void context and never assigned its return value, then it would never actually prompt the user for input! Well, glad we caught it now rather than it living on as an unintended feature. :-)sub foo(:t($temperature)) { ... } expects to be passed a named parameter t, but stores it in the scalar $temperature.$*IN, $*OUT and $*ERR as part of some work to generally improve interaction with things from outside of Rakudo in Parrot.I also during the day started moving bits of Rakudo’s I/O into the Raku setting. There are some bits of embedded PIR, but very little, since the handle we store is a Parrot I/O object which we are able to call methods on anyway. I’m hopeful that we can have all of I/O moved into the setting and written mostly in Raku in the near future.
Finally, in the evening and once my headache had gone, I worked out a very first cut of importing. It only imported things set to be exported by default, and didn’t have handling of multis quite right, but it laid the foundations for further work in the area.
Thanks to Vienna.pm for sponsoring this work.