Open GoogleCodeExporter opened 9 years ago
I think on reflection that you're right about being there in all cases.
It also seems odd to set up a killlist with options fetched from the config,
then pass that to the killlisttable which is what the config options are for.
So, I'm trying to add this as an inherent part of the killlisttable. The
downside is that without rewriting some of the core killlist code,
KilllistTable must be passed the killlists before they are passed to
pagesplitter. The need for this is not obvious so could easily cause problems.
Original comment by kovellia
on 17 Dec 2011 at 3:12
You are probably right regarding pushing config options as low as they can go
on the execution tree, but it's a really low priority so I wouldn't sweat it.
Original comment by jjl...@gmail.com
on 19 Dec 2011 at 1:49
Original issue reported on code.google.com by
jjl...@gmail.com
on 14 Dec 2011 at 4:11