X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=src%2Foutput%2Fdriver-provider.h;h=3712663bc5dcc8f95ad7ba2b7598e0767bb82e62;hb=507ebaea3673;hp=0f01fa9b30438f083ebf5865d3c5c8509b4df970;hpb=37a3446f43f6572f05783972df75ba6b9d1a0bea;p=pspp

diff --git a/src/output/driver-provider.h b/src/output/driver-provider.h
index 0f01fa9b30..3712663bc5 100644
--- a/src/output/driver-provider.h
+++ b/src/output/driver-provider.h
@@ -24,6 +24,7 @@
 #include "output/driver.h"
 
 struct output_item;
+struct output_iterator;
 struct string_map;
 struct file_handle;
 
@@ -73,8 +74,17 @@ struct output_driver_class
        it doesn't make sense for DRIVER to be used this way, then this function
        need not do anything. */
     void (*flush) (struct output_driver *driver);
-  };
 
+    /* Ordinarily, the core driver code will skip passing hidden output items
+       to 'submit'.  If this member is true, the core driver hands them to the
+       driver to let it handle them itself. */
+    bool handles_show;
+
+    /* Ordinarily, the core driver code will flatten groups of output items
+       before passing them to 'submit'.  If this member is true, the core
+       driver code leaves them in place for the driver to handle. */
+    bool handles_groups;
+  };
 
 /* An abstract way for the output subsystem to create an output driver. */
 struct output_driver_factory