On 2015-01-27 04:54, Zach the Mystic wrote:
It's only creepy if it doesn't work. And the compiler doesn't need to
change the code itself - it merely needs to tell you exactly what to do
to fix it.
I've thought about this some more. The way I would do it is have the
compiler store all files which need to be fixed. Output the list in
another file of a different type. Have dfix be able to read that file
and automatically fix all files listed. Or just generate a D script to
do just that (no need for a whole different file format. Literally just
output "dfix.d", which has all the filenames built right into the
script, and tell the user to 'dmd -run dfix.d'. Now you have a very
clear intermediate step between compilation and user-activated step.
Seems overly complicated. How about the compiler just outputs new files
instead.
--
/Jacob Carlborg
