Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It’s always a good idea to try to structure your output into some form of regular patterns. The human eye and brain are mindblowingly capable pattern matchers; heck, we compulsively try to find patterns in noise that has none. Opting to take advantage of this is quite the opposite of a bad idea.

    In any case, if you did want to use automated testing, in your case, in order to catch the most low-hanging fruit among bugs if not all of them, you will probably need to link against some reference implement

    • Hmmm, that's not a bad idea. With a recent Mesa, I should be able to use the off-screen renderer, which one would hope is independent of the settings of the desktop frame buffer (if not, this becomes a non-starter, I think). It does represent an extra dependency (and a non-trivial one at that), but it still may be worth it.

      I guess it depends on how stable the output of the off-screen renderer has been across Mesa versions. If the rendering of existing features has been solid (and seems likely to remain so), the worries about driver updates messing with the reference images are much reduced.

      Thanks for the suggestion!