|
irclog.perlgeek.de/perl6book/today | source: github.com/perl6/book/ Set by moderator on 20 August 2010. |
|||
|
05:02
mfollett joined
|
|||
| mfollett | I've added a section on single inheritance to the Perl 6 book, who do I send a pull request? | 05:03 | |
|
05:15
mfollett left
05:46
mfollett joined
06:02
mfollett left
07:39
pronik joined
07:46
pronik left
07:56
pronik joined
08:12
pronik left
11:09
mfollett joined
11:13
mfollett left
11:15
mfollett joined,
mfollett left
12:55
masak joined
14:01
mfollett joined
|
|||
| mfollett | Hey, I added a section on single inheritance. Who do I send a pull request to for them to look it over? Sorry for asking this question twice for those who have been on since midnight. | 14:02 | |
| moritz_ | mfollett: to the same account that holds the book repo | 14:03 | |
| ie perl6 | |||
| mfollett | Ok, I started to do that and it had a whole list of people it was going to send the request to. I wanted to check to make sure I wasn't spamming a bunch of people. | 14:04 | |
| moritz_ | hm | ||
| you can also look at the list of authors | |||
| mfollett | and by midnight I meant midnight GMT-5 | ||
| moritz_ | github accounts: moritz masak perlpilot jnthn pmichaud | 14:05 | |
| mfollett | oops, I just sent it. In the future I will only send it to those 5. | 14:06 | |
| moritz_: thanks for the info | 14:07 | ||
| moritz_ | +to inherit from multiple classes. When a class inherits from another class it | 14:16 | |
| 356 | |||
| +acquires all of the attributes and methods of the base class. | |||
| that is not very precise | |||
| masak | I'm reading the Camel book right now. only on chapter 1 so far, but it's really, really good. | ||
| I think we should strive for that kind of tone/prose. | |||
| moritz_ | attributes are not inherited | ||
| only accessors are | |||
| and methods aren't really acquired either - it's rather that the dispatcher also considers the parent class | 14:17 | ||
| masak: agreed that Camel is great. Disagreed on striving for the same tone - at least for now. We should really get the book in a shape so that it can be printed. | 14:18 | ||
| masak | agreed on that. though I maintain that the way to that print-ready state involves making the tone much more coherent and readable anyway. | 14:19 | |
| I'm all for deadlines, but I'd rather hold the printing off a bit if it means significant improvement to the text. | 14:20 | ||
| moritz_ | the problem is that we don't have deadlines | ||
| we had some, and missed them | |||
| and now there's no significant event to synchronize with | |||
| masak | aye. that is a problem. | 14:23 | |
| maybe we should declare one of the coming Star releases "the book release"? | 14:24 | ||
| with sufficient empirical reasons for the choice of the particular release. | |||
| moritz_ | do we have sufficient empirical reasons? :-) | ||
| masak | we could try to winnow some. and if those turn out to be wrong, we'll have better ones for next time. :) | 14:26 | |
| mfollett | moritz_: Alright, thanks for the review, I'll rewrite it to be more specific. | 14:40 | |
| moritz_ | mfollett: great | ||
| mfollett: if would also be nice if the child class added something to the parent class, so that there's a practical reason for inheritance | |||
| mfollett | mortiz_: That's a good point, I will do that too. | 14:42 | |
|
15:16
lucs left
16:24
masak left
22:49
mfollett left
|
|||