42

I've been googling around and I just can't find a simple answer to this. And it should be simple, as the STL generally is.

I want to define MyOStream which inherits publicly from std::ostream. Let's say I want to call foo() each time something is written into my stream.

class MyOStream : public ostream {
public:
  ...
private:
   void foo() { ... }
}

I understand that the public interface of ostream is non-virtual, so how can it be done? I want clients to be able to use both operator<< and write() and put() on MyOStream and have use the extended ability of my class.

Michael
  • 2,586
  • 4
  • 23
  • 17
  • 3
    The STL might be simple, but that's only one part of the C++ standard library. The iostreams library have nothing to do with (what was once) the STL. STL is basically contianers + iterators + algorithms. Iostreams, locales and all that has a completely different origin, and is generally a pain to work with ;) – jalf Apr 21 '09 at 14:21

5 Answers5

45

I was spinning my head around how to do the same thing and i found out it's actually not that hard. Basically just subclass the ostream and the streambuf objects, and construct the ostream with itself as the buffer. the virtual overflow() from std::streambuf will be called for every character sent to the stream. To fit your example i just made a foo() function and called it.

#include <iostream>

struct Bar :  private std::streambuf , public std::ostream
{
    Bar() : std::ostream(this) {}

private:
    int overflow(int c) override
    {
        foo(c);
        return 0;
    }


    void foo(char c)
    {
        std::cout.put(c);

    }
};

int main()
{
    Bar b;
    b<<"Look a number: "<<std::hex<<29<<std::endl;

    return 0;
}

EDIT: The old code used the wrong initialization order. Although it had no visible side effects, the streambuf object should be initialized before passing it to the ostream object. Since C++ initializes parents left to right, I moved std::streambuf to the left to make the code correct.

EDIT: I changed the code to inherit std::streambuf privately to keep the interface cleaner and keep the class encapsulated.

Ben
  • 817
  • 8
  • 9
  • 4
    Works perfectly! Should be the accepted answer, though it is an old question. – ZXcvbnM Sep 12 '15 at 17:40
  • I agree with ZXcvbnM, this should be the accepted answer. The accepted answer contains a useful reference but does not really provide a solution. Ben provides a simple working solution. +1. – sgbirch Jun 06 '17 at 07:15
  • Finally I found a solution after looking for it for so long time, this should be the accepted answer like people said. – user0103 Dec 12 '17 at 11:58
  • Many thanks! After such a long time I finally found a solution in this answer. This should be the accepted one. – Ruurd Adema Dec 04 '18 at 11:26
  • 1
    I guess one usually does not want clients to use `Bar` as `std::streambuf`. In this case private inheritance seems like the way to go: `class Bar : private std::streambuf, public std::ostream {};` – Brandlingo Mar 20 '20 at 10:59
  • @MatthäusBrandl You're right. I updated the code. Plus i added the added methods into the private space. It makes the interface much cleaner. Thanks for the pointing that out. – Ben Nov 14 '20 at 02:37
  • Calling put() for every character that is put into the stream is very slow. – somega May 19 '22 at 14:15
26

It's not a simple question, unfortunately. The classes you should derive from are the basic_ classes, such as basic_ostream. However, derivation from a stream may not be what you want, you may want to derive from a stream buffer instead, and then use this class to instantiate an existing stream class.

The whole area is complex, but there is an excellent book about it Standard C++ IOStreams and Locales, which I suggest you take a look at before going any further.

Qix - MONICA WAS MISTREATED
  • 13,194
  • 13
  • 82
  • 139
21

Another working hack to achieve a similar effect is to use template and composition

class LoggedStream {
public:
  LoggedStream(ostream& _out):out(_out){}
  template<typename T>
  const LoggedStream& operator<<(const T& v) const {log();out << v;return *this;}
protected:
  virtual void log() = 0;
  ostream& out;
};

class Logger : LoggedStream {
  void log() { std::cerr << "Printing" << std::endl;}
};

int main(int,char**) {LoggedStream(std::cout) << "log" << "Three" << "times";}
Elazar Leibovich
  • 31,610
  • 30
  • 120
  • 165
6

I don't know if this is correct solution, but I inherited from std::ostream this way. It uses a buffer inherited from std::basic_streambuf and gets 64 characters at a time (or less if flushed) and sends them to a generic putChars() method where the actual handling of data is done. It also demonstrates how to give user data.

Live Example

#include <streambuf>
#include <ostream>
#include <iostream>

//#define DEBUG

class MyData
{
    //example data class, not used
};

class MyBuffer : public std::basic_streambuf<char, std::char_traits<char> >
{

public:

    inline MyBuffer(MyData data) :
    data(data)
    {
        setp(buf, buf + BUF_SIZE);
    }

protected:

    // This is called when buffer becomes full. If
    // buffer is not used, then this is called every
    // time when characters are put to stream.
    inline virtual int overflow(int c = Traits::eof())
    {
#ifdef DEBUG
        std::cout << "(over)";
#endif
        // Handle output
        putChars(pbase(), pptr());
        if (c != Traits::eof()) {
            char c2 = c;
            // Handle the one character that didn't fit to buffer
            putChars(&c2, &c2 + 1);
        }
        // This tells that buffer is empty again
        setp(buf, buf + BUF_SIZE);

        return c;
    }

    // This function is called when stream is flushed,
    // for example when std::endl is put to stream.
    inline virtual int sync(void)
    {
        // Handle output
        putChars(pbase(), pptr());
        // This tells that buffer is empty again
        setp(buf, buf + BUF_SIZE);
        return 0;
    }

private:

    // For EOF detection
    typedef std::char_traits<char> Traits;

    // Work in buffer mode. It is also possible to work without buffer.
    static const size_t BUF_SIZE = 64;
    char buf[BUF_SIZE];

    // This is the example userdata
    MyData data;

    // In this function, the characters are parsed.
    inline void putChars(const char* begin, const char* end){
#ifdef DEBUG
        std::cout << "(putChars(" << static_cast<const void*>(begin) <<
            "," << static_cast<const void*>(end) << "))";
#endif
        //just print to stdout for now
        for (const char* c = begin; c < end; c++){
            std::cout << *c;
        }
    }

};

class MyOStream : public std::basic_ostream< char, std::char_traits< char > >
{

public:

    inline MyOStream(MyData data) :
    std::basic_ostream< char, std::char_traits< char > >(&buf),
    buf(data)
    {
    }

private:

    MyBuffer buf;

};

int main(void)
{
    MyData data;
    MyOStream o(data);

    for (int i = 0; i < 8; i++)
        o << "hello world! ";

    o << std::endl;

    return 0;
}
JDW
  • 440
  • 3
  • 11
Henrik Heino
  • 367
  • 4
  • 8
  • This is flawed. You are passing `basic_ostream` a pointer no a not yet constructed buffer, since the base class is initialized before the data member. See [Ben's answer](https://stackoverflow.com/a/19933011/1969455) for more on this. – Brandlingo Mar 20 '20 at 10:50
-2

Composition, not inheritance. Your class contains, "wraps" an ostream&, and forwards to it (after calling foo()).

tpdi
  • 33,714
  • 11
  • 78
  • 117
  • 1
    Please post some code that illustrates how this would work with the existing << operators. And note foo() is to be called each time such an operator is used. –  Apr 21 '09 at 12:50
  • 8
    Composition is not always the best solution, just as inheritance isn't. ostream has a dozen of overloaded operators implemented for it, you don't expect anyone to really rewrite all the public interface of ostream just to add a small functionality to a class. – Michael Apr 21 '09 at 12:58
  • 3
    There's also the issue that people write their own operator<< methods that assume an ostream. If you're not actually an ostream, those won't get invoked. – Joseph Larson May 08 '18 at 13:02