irclog.perlgeek.de/perl6book/today | source: github.com/perl6/book/
Set by moderator on 13 December 2009.
06:16 hicx174 joined 08:07 masak joined 10:16 snearch joined 13:37 masak joined
dalek ok: 680b5b8 | duff++ | docs/announce/2009-11:
belated checkin of Nov release announcements
14:18
ok: a6ee18a | duff++ | src/preface.pod:
Merge branch 'master' of git@github.com:perl6/book
ok: c40a1dd | masak++ | docs/release-guide.pod:
[docs/release-guide.pod] instructions to push announcement
14:30
ok: 69a026a | masak++ | docs/announce/2009-12:
[docs/announce/2009-12] created announcement
14:42
masak 'ppreciate it if someone would take a look at the announcement: github.com/perl6/book/blob/69a026aa...ce/2009-12
I haven't built the PDF yet, but I will now.
jnthn masak: Looks fine to me. :-) 14:46
masak \\o/
having build problems :( 14:59
gist.github.com/259538
moritz_ masak: works here 15:00
15:00 aigon joined
moritz_ masak: is book.tex created? 15:00
masak looks
moritz_ in build/ 15:01
masak yes, but it was empty.
moritz_ oh
masak I removed it, now I get another error.
moritz_ it shouldn't be
masak hm.
it still doesn't find Pod::PseudoPod::LaTeX.
ah. fixed. much better now. 15:02
I think I just encountered the strangest bug of 2009. 15:08
when uploading the file to github, I found I couldn't type lower-case 's' in the 'Description' text box. 15:09
every time I did, focus jumped to the Search Box on github.
in the end, I had to paste an 's' through the context menu.
hm. I don't think I have a rakudo.org account, after all. 15:13
should I try to get one, or should I delegate the posting?
moritz_ how did you post the release announcement for the rakudo release?
masak everything's set now; only the posting remains.
moritz_ anyway, I can post it for you if you don't have permission 15:14
masak danke. 15:15
moritz_: I didn't. jnthn did. 15:16
my computer had just run out of battery at that point.
moritz_ rakudo.org/node/62 15:17
there you go
masak thanks! 15:23
moritz_++ 15:24
moritz_ masak++ for doing the release 15:25
up for some discussion? 18:33
jnthn I sorta need to run to the shop, but will be back in 15-20... 18:35
Or if it's quick discussion can do now before I go
moritz_: book planning, I'm guessing? 18:36
moritz_ yes 18:37
about the description of builtins
should it go into the first chapter? or be a chapter of its own?
jnthn Hmm. Is the intention to have a full list of the built-ins? 18:42
It feels more appendix-ish ot me. 18:43
*to me
As in, it's kinda referenece material-ish. 18:44
Rather than the style of the rest of the chapters.
brb, nomshop 18:45
moritz_ well 19:03
I tried to re-read the first chapterl, and pretend that I have no knowledge of Perl 6
and I found that I couldn't solve the excercises
because it needs boolean negation, and that hasn't been introduced yet 19:04
so I think we need to establish a base line
not all builtins 19:05
just the important ones
jnthn moritz_: Ah, OK, that's a fair point. 19:10
moritz_ so since it doesn't have a major example, maybe merge it into the first chapter?
but it doesn't fit well from the flow of things
jnthn Yeah 19:11
And if the first chapter doesn't flow nicely, it's hardly good for drawing folks into the rest of the book.
moritz_ so, how do we solve this? 19:21
jnthn Could we have exercises that don't rely on built-ins that weren't covered? Or maybe in the question say in parens like (You can use the X built-in to Y) 19:28
as a hint
moritz_ well, since we cover nearly no builtins in chapter one, the first alternative is kinda hard 19:29
and even if we introduce some to make the questions work, that's still not enough to enable people to write code on their own
19:36 japhb joined
jnthn ah, true 19:41
22:34 d4l3k_ joined, pmichaud_ joined 22:35 p6eval joined