leanpub.com/perl6 | logs at irclog.perlgeek.de/perl6book/today | announcement at perlgeek.de/blog-en/perl-6/2016-book.html
Set by moderator on 3 January 2017.
02:49 ilbot3 joined
moderator leanpub.com/perl6 | logs at irclog.perlgeek.de/perl6book/today | announcement at perlgeek.de/blog-en/perl-6/2016-book.html
[ptc] silly question time: in the variable $.exitcode, the `.` is actually a twigil (not a sigil), isn't it? 06:54
also, what do the 'I>' markers mean? That doesn't look like markdown... 06:56
SQLite is used on some airliners?? Do you have a reference for that? 07:36
07:40 FROGGS joined
[ptc] moritz: I should have pinged you directly wrt the questions above. I can post them again if you've missed them. 13:09
moritz [ptc]: yes, the . is a twigil
[ptc] moritz: I can then hopefully finish the proof reading on the way home tonight 13:10
moritz [ptc]: the I> markers are a LeanPub extension to markdown, and mark an "info" section
[ptc] cool! Ta :-)
moritz [ptc]: re SQLite, I heard that in an interview with the SQLite creator on some podcast
[ptc] no rush! Just wanted to ping you so you knew that I'd made noise in the channel :-) 13:11
moritz [ptc]: sure, appreciated
www.sqlite.org/famous.html "Airbus confirms that SQLite is being used in the flight software for the A350 XWB family of aircraft." 13:16
[ptc] geil. Danke! 13:21
moritz: what's the motivation for using a class when testing the silent cron program? Is it so that the testing is easier? 16:15
moritz: just felt that at the beginning of the discussion that the motivation was missing slightly 16:16
moritz: have proof read the two new silent-cron blog posts. Not much to change; it's good stuff. Clearly written, good logical flow. 16:36
moritz [ptc]: thanks 19:08
[ptc]: I'll try to clarify the motivation a bit
[ptc] moritz: is there anything else you would like me to read over? In other words: have I missed anything in the blog posts? 19:18
moritz [ptc]: there's blog/silent-cron-state.md 19:24
:-)
[ptc] moritz: done that one :-) 19:32
moritz [ptc]: ah, great
[ptc]: then you've caught up to me 19:33
moritz reviews the review
[ptc] okey dokey 19:34
if you've got any questions, or want me to change anything, just let me know 19:35
moritz I guess "what should I write next?" isn't a question you can answer? :-) 19:36
[ptc] actually, I'd been wondering about pattern matching. 19:39
I mean, Perl is traditionally a language for text munging and showing people how to use the current regexp stuff would probably be a good idea 19:40
or have I completely forgotten that you've already covered that?
moritz indeed I haven't 19:41
the examples I've had in mind for that turned out to have much simpler solutions (.lines and .split, mostly)
[ptc] I don't know if one needs to go deeply into grammars, however using the current regexp stuff would definitely be helpful, especially for P5 people making the conversion 19:42
moritz maybe I should just do something dumb and develop yet another INI parser
[ptc] YAIP
how about roles? 19:43
like a task which could be well solved via composition instead of inheritance
moritz roles are vaguely on my agenda too, but so far I haven't thought of examples that might benefit from them 19:44
I haven't used inheritance yet either
[ptc] I liked your example of finding pi by throwing random data at the unit square; there's an interesting example in (I think) numerical recipes about finding the volume of a torus 19:47
maybe something like that would be interesting, especially to show off how easy it is to do parallel programming
moritz yes, that might be an option 19:48
regarding grammars, things i've considered: 19:50
csv: too many variants, little intrisic complexity => not a good fit for grammars
ini: might be OK. No real spec though 19:51
json: beaten to death already
I wonder if there's a programming languge that's surprisingly easy to parse with grammars 19:52
like Pascal maybe
[ptc] dave cross used an example of translating British English into American English in Munging Data with Perl. Maybe that's an idea 19:53
it's a bit amusing and yet could still require a grammar to do the translation 19:54
another example was parsing /etc/passwd 19:55
moritz www.cs.utexas.edu/~novak/grammar.html not very complicated, but too much for a book example
[ptc] what about an example with Inline::Perl5? 19:56
just to underline the bridges between the two Perls
moritz also a good idea 19:57
www.adobe.com/products/postscript/pdfs/PLRM.pdf # postscript is also too complex to parse 20:07