Rework DumpTarget for YAPF debugging output
commitec257778289f6920702bbfbaff50d04fb0c2295e
authorcirdan <cirdansw@gmail.com>
Sat, 1 Mar 2014 07:32:13 +0000 (1 08:32 +0100)
committercirdan <cirdansw@gmail.com>
Sat, 1 Mar 2014 07:32:13 +0000 (1 08:32 +0100)
treefd3b1ae4e1ca75c229c2b9ce926551aca5e9b48a
parent46b2e88db37eaa5c1efcf52f41ba8b66be6a1836
Rework DumpTarget for YAPF debugging output

The way in which YAPF state was output for debugging was just
plain insane. The code would construct one huge string in memory
for each of two pathfinders and them dump them whole to one file
each, without even caring to handle them sequentially. Instead,
we now have the dump code directly write the data to a file as
they are generated.
src/misc/dbg_helpers.cpp
src/misc/dbg_helpers.h
src/pathfinder/yapf/yapf_rail.cpp