search for: ownsstream

...should not manage the + /// held stream. + /// + static const bool REFERENCE_ONLY = false; + + private: + /// TheStream - The real stream we output to. We set it to be + /// unbuffered, since we're already doing our own buffering. + /// + raw_ostream *TheStream; + + /// OwnsStream - Are we responsible for managing the underlying + /// stream? + /// + bool OwnsStream; + + /// BufferSize - The size of the buffer in bytes. + /// + size_t BufferSize; + + /// BufferArray - The actual buffer storage. + /// + char *BufferArray; + + /// Cur - Pointer to...

...' like TAKES_OWNERSHIP? "preservation" isn't > really the same as "not deleting when the stream is destroyed" to me. That's a good idea. I just took these from what Dan (I think) did in formatted_raw_ostream. I'll change them here and rename DeleteStream to OwnsStream as well. > > + /// TheStream - The real stream we output to. We set it to be > > + /// unbuffered, since we're already doing our own buffering. > > + /// > > + raw_ostream *TheStream; > > Now that I understand the model :) I don't see why you need...

...he elements of a vector<T*> are owned or unowned) > ASTUnit::OwnsRemappedFileBuffers > VerifyDiagnosticConsumer::OwnsPrimaryClient > TextDiagnosticPrinter::OwnsOutputStream > FixItRewriter::OwnsClient > Tooling::OwnsAction > > Some in LLVM: > > circular_raw_ostream::OwnsStream > Arg::OwnsValues (another tricky one with a bool flag and a vector of raw > pointers, if I recall correctly) > > > And a couple that I changed {T*, bool} to {T*, unique_ptr<T>}: > > LogDiagnosticPrinter::StreamOwner > ASTUnit::ComputedPreamble::Owner > > On Wed,...

[+cfe-dev] This conversation has already been happening on llvm-dev so there's no good way for me to capture the entire existing discussion (so I'm jumping you in part-way) & the subject line could be more descriptive, but I wanted to add Clang developers since many of the interesting cases of conditional ownership I've seen were in Clang. I know some of you are also on llvm-dev

On Dec 18, 2009, at 3:46 PM, David Greene wrote: > > + /// circular_raw_ostream - A raw_ostream that saves its output in a > + /// circular buffer. A better description would be "which *can* save its data to a circular buffer, or can pass it through directly to an underlying stream if specified with a buffer of zero." When it is buffering, what causes it to flush? Your

...e owned or unowned) >> ASTUnit::OwnsRemappedFileBuffers >> VerifyDiagnosticConsumer::OwnsPrimaryClient >> TextDiagnosticPrinter::OwnsOutputStream >> FixItRewriter::OwnsClient >> Tooling::OwnsAction >> >> Some in LLVM: >> >> circular_raw_ostream::OwnsStream >> Arg::OwnsValues (another tricky one with a bool flag and a vector of raw >> pointers, if I recall correctly) >> >> >> And a couple that I changed {T*, bool} to {T*, unique_ptr<T>}: >> >> LogDiagnosticPrinter::StreamOwner >> ASTUnit::ComputedP...

On Friday 18 December 2009 17:27, David Greene wrote: > > Here's the updated patch. > > Well, that didn't go through right. Here it is again. Argh! Stupid bug fixed. :) Index: include/llvm/Support/circular_raw_ostream.h =================================================================== --- include/llvm/Support/circular_raw_ostream.h (revision 0) +++

On Wed, Oct 1, 2014 at 3:14 PM, Anton Yartsev <anton.yartsev at gmail.com> wrote: > Ping! > > Suggested is a wrapper over a raw pointer that is intended for freeing > wrapped memory at the end of wrappers lifetime if ownership of a raw > pointer was not taken away during the lifetime of the wrapper. > The main difference from unique_ptr is an ability to access the wrapped