> Recently, I explored ways of splitting the fuzz targets that keep > engineering and runtime overhead at a minimum [...] At this point, > I am convinced that my current approach (strategy/iterator/visitor) > is flexible enough to provide everything that will be needed from > the fuzz targets while it adds only a moderate code overhead.
Looks good! Are you going to document your approach in `freetype2-testing's `README.md' file? > Also: currently, I keep track of all (un)used interface functions of > FreeType (`FT_*') internally. The plan is to migrate this overview > to the README.md to add some transparency about what is > (technically) covered and what is missing. Excellent! > Feel free to have a look at https://github.com/cherusker/freetype2-testing > (esp. fuzzing/src) and feedback as you see fit: code style, comments, OOP, > C++, etc. I am always happy to exchange thoughts :) Everything looks very clean :-) Werner _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
