[Home]BoostCon 2007/Container Printing Lib - Interface And Concepts

BOOST WIKI | BoostCon 2007 | RecentChanges | Preferences | Page List | Links List

Difference (from prior major revision) (no other diffs)

Changed: 70c70
See Hartmuts and Joaos implementation...
See Hartmut's and Joao's implementation...

Changed: 73c73
explore offers a number of locations where it's behavior can be modified or extended:
explore offers a number of locations where its behavior can be modified or extended:

Printing Library Interface

This page describes a proposal for the interface of the (Container-) printing library, some of the concepts and some of the variation points where different or new behavior can be plugged in.


example usage:

  using namespace explore;

  // ... some container c defined here

  print( c, std::cerr, html_table_format());

full argument list of print (informal, declaration follows later):

  print( item, stream = std::cout, format = default_format(), element_policy = default_policy())

The print function will either:

Element Policy

print approaches the items that it must print as one of the following: An item can be a printable, a container or none of those two (in which case print() can not print it)

An element policy tells the print function if an object is printable, a container or none. It does this by wrapping two unary metafunctions: is_printable<T> and is_container<T>. The implementations of these metafunctions in the default policy delegate their decision to the "global" metafunctions explore::is_printable and explore::is_container respectively:

 struct default_policy
    template< typename T>
    struct is_printable : explore::is_printable<T>

    template< typename T>
    struct is_container : explore::is_container<T>

The definitions of the "global" metafunctions are such that a type is by default printable if there is a stream output operator for the type and it is a container if it fits the range concept. By default tuples (and std::pair) will be treated as ranges.

Note that the previous paragraph implies that std::string will be streamed directly and not as a container of characters. If I want the characters of a string to be printed separately (and be subject to formatting), I could define the following policy:

  struct string_as_container : explore::default_policy
      struct is_printable<std::string> : mpl::false_

      // default is fine for is_container

  print( std::string("hello"));
  // outputs: hello

  print( std::string("hello"), std::cout, /*default_format(), */string_as_container());
  // outputs something like: [ h, e, l, l, o ]


Formatting is very much subject to the reality check (read: implementation) that is being performed as I write this page. While formatting the output an important thing to keep in mind is the dimension or depth of the container (or printable) that is being printed. A vector<vector<std::string> > by default has depth 2, but note that under the string_as_container policy that same type will have depth 3.

Formatting is specified in terms of karma generators.

In general terms: a format given to print is in fact a karma generator generator (referred to as 'instant karma' in the rest of this text). print will recursively call print_container, which may in turn call print. At every level, a slightly modified version of the instant karma is handed to the next version. This way, at compile time a karma generator is created that can handle an object of the dimension that was given to the print function.

See Hartmut's and Joao's implementation...

Variation Points

explore offers a number of locations where its behavior can be modified or extended:


BOOST WIKI | BoostCon 2007 | RecentChanges | Preferences | Page List | Links List
Edit text of this page | View other revisions
Last edited May 15, 2007 11:53 pm (diff)
Disclaimer: This site not officially maintained by Boost Developers