|
weekly Perl 6 status meetings with phase transitions: Tue 19:00 UTC | IR clogs at irclog.perlgeek.de/phasers/today Set by moderator on 14 June 2011. |
|||
|
00:20
[particle]1 joined
00:21
[particle] left,
[particle]1 is now known as [particle]
00:41
[particle] left,
[particle] joined
07:55
Util left
07:57
Util joined
15:52
[particle] left
15:53
[particle] joined
15:56
mberends joined
18:16
benabik joined
18:20
colomon joined
18:51
masak joined
|
|||
| masak | pre-report: I blogged, once. another blog coming up. hoping to get some Perl 6 hacking done in general. maybe even som hacking on nom, we'll see. EOR | 18:52 | |
| pmichaud | pre-report: | 18:53 | |
| What I did: | 18:54 | ||
| nom stuff: | |||
| * With jnthn++, added basic regex support | |||
| * Updated Str.Numeric to return correctly typed numifications | |||
| nqp stuff: | |||
| * Added an opcode to simplify numeric radix conversions | |||
| other stuff: | |||
| * Wrote some blog posts | |||
| * Planning for releases in July and August | |||
| What I plan to do: | |||
| * nom protoregexes | |||
| * more spectests | |||
| * presentation at FOSSCON in Philadelphia | |||
| EOR | |||
| Also, I'm looking for comments/improvements to pmichaud.com/sandbox/rel.txt | |||
|
18:54
masak__ joined
|
|||
| Util | Pre-report: Smoke testing & Win32 debugging for Parrot release. | 18:55 | |
| Uploaded pics from YAPC::NA Parrot/Perl6 BOF and dinner picasaweb.google.com/104678127090280812061/ | 18:56 | ||
| EOR | |||
| mberends | pmichaud: +1 to rel.txt (you even say "couple of weeks", not "couple weeks" :) | ||
|
18:56
masak left
|
|||
| mberends | o/ | 19:00 | |
| masak__ | o/ | ||
| Util | o/ | ||
| tadzik | o/ | ||
| PerlJam | greetings | ||
| moritz | \\o | 19:02 | |
| pmichaud | \\o/ | ||
| mberends | ok if I report? | 19:03 | |
| moritz | sure | ||
| mberends | Done (in 6model/c): | ||
| * Made a minimalistic implementation plan (not written up yet) | |||
| * Figured out how to compile and execute C code on the fly | |||
| * It uses dlopen() on Unix and LoadLibrary() on Windows | |||
| * Works with gcc on Unix and either gcc or msvc on Windows | |||
| sorear | o/ | ||
| mberends | * Add an already written hashtable library and test it | ||
| * Design a refcount based heap manager and test it | |||
| * Build a SerializationContext on them and access it from generated C | |||
| .EOR | |||
| pmichaud | niiiiiice mberends++ | 19:04 | |
|
19:04
masak__ is now known as masak
|
|||
| moritz | mberends++ and pmichaud+ | 19:04 | |
| erm | |||
| pmichaud++ | |||
| my report: | |||
| sorear | mberends++ # sounds a lot like one of my plans | ||
| moritz | fiddled with nom built-ins | ||
| now trying to add back regex related functions | 19:05 | ||
| EOR | |||
| tadzik | 19:09 | ||
| did: passed the gsoc midterms | |||
| vacationed after the midterms a bit | |||
| plans: more vacationing, sweetened with an adequate amount of gsoc hacking | 19:10 | ||
| =end report | |||
| masak | \\o/ | ||
| tadzik++ | |||
| sorear is embarrased to admit having done very little | 19:11 | ||
| masak | sorear: do you have any plans to one-up Rakudo on any particular features? | 19:12 | |
| TimToady | well, it's been one-up on error messages for a while now, not to mention threads | 19:16 | |
| PerlJam | pmichaud: +1 re rel.txt (looks good) | 19:17 | |
| masak | indeed, pmichaud++ | ||
|
19:18
[particle] left
|
|||
| pmichaud | not seeing/hearing any changes to rel.txt, will post shortly. | 19:19 | |
| Util | +1 on rel.txt. | 19:21 | |
|
19:21
[particle] joined
|
|||
| moritz was +1 on rel.txt last time he read it, hasn't reread it since then | 19:25 | ||
| anything else we need to discuss today? | |||
| sorear | masak: define one-up | 19:26 | |
| masak | sorear: in this context: Rakudo doesn't implement the feature, but niecza does. | ||
| I mean it in the "friendly comparison" sense, not in a "let's see who wins" sense. | 19:27 | ||
| PerlJam | pmichaud: regarding the distribution name ... why not stick with R* ? | 19:28 | |
| masak | well, if there was ever a reason to switch names, this is one. that's not to say that it's reason enough, of course. | 19:30 | |
| pmichaud | PerlJam: we don't want R* to regress, so we can only (re)use R* when the module ecosystem is at least as good as what R* has today. | 19:31 | |
| Util | Sticking with R* means continuity, and less to explain to users. | ||
| masak kinda liked "Rakudo Moon" | |||
| pmichaud | "means continuity" -- yes, but only if achieving continuity is in fact possible and timely :) | 19:32 | |
| if it takes us six months to achieve continuity... that might be too long. | |||
| TimToady | sorear: or look at it more like this: "Which parts of the problem space are you currently researching that we can all learn from later?" :) | ||
| PerlJam | pmichaud: rakudo regressed when we went from alpha to ng, we still called it "rakudo" :) | ||
| anyway, the reason I ask is that it seems to me that we lose a little in branding if use a different name. | 19:33 | ||
| mberends | pmichaud: do you expect to have time to work on fixing Zavolaj or Parrot NCI this week? I'm available until the weekend, and would like to get MiniDBI working again for R*. | ||
| PerlJam | (unless the new thing is far and away better than the old thing) | ||
| pmichaud | PerlJam: we make a distinction between the compiler and distributions, though (more) | 19:34 | |
| compilers are allowed to be a bit more unstable than distributions are intended to be | |||
| mberends: this week, unlikely. next week, possible. | |||
| this week I really need to focus on getting protoregexes in place (faster compiles!), and then I'll be travelling to a conference | 19:35 | ||
| *traveling | |||
| mberends | pmichaud: next week is randomly possible for me too | ||
| pmichaud | well, fixing up zavolaj would certainly be a Jul 30 candidate task, too. :) | ||
| having looked at zavolaj recently, I don't think it'll be at all hard to port. | 19:36 | ||
| PerlJam: I see "rakudo" as an umbrella name for multiple products | |||
| so the fact that it remains the same is... expected :) | |||
| rakudo.org/2011/07/19/upcoming-rakudo-releases/ # fyi, now posted | 19:39 | ||
| anyway, what to call the next distribution release may end up having to be a decision we make in early August, as we get a feel for how close we come to the existing Star release | 19:40 | ||
| I agree that a new name requires some explanation to users, but so does "well, this no longer works, and ABC now works like DEF, and ..." | |||
| sorear | TimToady: afaik, the *only* place where that has happened is ltm | 19:42 | |
| masak | sorear: I'm asking because I want to dig into some parts of S09, and mulling over whether to contribute to Niecza or Rakudo. | 19:43 | |
| sorear | masak: what parts of S09 are you looking at? | 19:45 | |
| I haven't really looked at S09 from an implementation perspective at all yet | 19:46 | ||
| masak | I'd like to implement some of the indexing sugar for arrays and hashes. | ||
| should be fairly straightforward, because it's not really new features, just under-the-hood static translations. | 19:47 | ||
| pmichaud | q1q | 19:50 | |
| masak | pmichaud: shoot | 19:51 | |
| pmichaud | so far we don't have a release manager for this month. I'm happy to do it if nobody else is jumping to do it | ||
| tadzik | I can do that | 19:52 | |
| pmichaud | the release announcement will need a bit of crafting (to explain upcoming releases), but other than that it should be straightforward | 19:53 | |
| tadzik | oh wait, it's quite soon, I may not have internet access then | ||
| pmichaud | release is in 2 days, yes. :) | ||
| masak | (we're going to a primeval forest in the next few days) :) | 19:55 | |
| mberends | if you're still in the forest at release time, pass the release hat to me :) | 19:56 | |
| masak | we are. mberends++ | 19:57 | |
| mberends | ok, consider me volunteered. | 19:59 | |
| mberends tests whether a South African beer goes with a Release Manager hat | 20:00 | ||
| [Coke] suspects * Beer would. | 20:01 | ||
|
20:02
spinclad left
20:12
masak left,
spinclad joined
|
|||