[Hours] [Activity] 2012/08/06 Monday 0.25 investigating security tickets 1.00 reading/responding to list mail ===== 1.25 2012/08/07 Tuesday 3.75 -e 'BEGIN {1}' 2.75 reading/responding to list mail ===== 6.50 2012/08/08 Wednesday 0.25 -e 'BEGIN {1}' 0.50 process, scalability, mentoring 0.50 readonly ops 8.50 warnings from multi-line constructions ===== 9.75 2012/08/09 Thursday 0.50 process, scalability, mentoring 4.00 warnings from multi-line constructions ===== 4.50 2012/08/10 Friday 0.75 process, scalability, mentoring 3.00 warnings from multi-line constructions ===== 3.75 2012/08/12 Sunday 2.25 warnings from multi-line constructions ===== 2.25 Which I calculate is 28.00 hours Most of the week was taken up with investigating three related areas: *) How code such as -e 'BEGIN {1}' is compiled, and the interaction between PL_main_cv, CvSTART(PL_main_cv), PL_main_root and PL_main_start *) Code in op.c which calls CopLINE_set(PL_curcop, oldline) and warnings from multi-line constructions *) Building with -DPERL_DEBUG_READONLY_OPS to force shared ops to be read-only, and determining the causes of code trying to write to read-only ops all of which aren't quite finished yet (even 1.5 days into "next" week), so will have to wait until the next report for a (hopefully more) coherent narrative. The next report likely will be late as I'm at YAPC::Europe for most of next week. Nicholas Clark