When checking for errors, how about an option to give up after a configurable number of errors are found? One file I tested generated over 32 thousand errors. It would take less than 100 errors to convince me that the file was badly broken. Thanks.
Himmm.
It could be good feature. But DivFix++ is a dump program that works as smart ones. So it's fast (because of dump) and it makes it's job. But it doesn't know difference between JUNK sections are error or not. Even interleave marks are counted as errors. It mark this sections as error and remove them.
It can learn difference between this keywords and errors but it requires structural change. It means rewrite/refactor of some functions.Is it worth for that?
Yes you can implement skip after X error easily but it will not work as intended...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Himmm.
It could be good feature. But DivFix++ is a dump program that works as smart ones. So it's fast (because of dump) and it makes it's job. But it doesn't know difference between JUNK sections are error or not. Even interleave marks are counted as errors. It mark this sections as error and remove them.
It can learn difference between this keywords and errors but it requires structural change. It means rewrite/refactor of some functions.Is it worth for that?
Yes you can implement skip after X error easily but it will not work as intended...