Dylan Trotter wrote:
Stefan Seefeld wrote:
Dylan Trotter wrote:
The more I think about this problem, the more I think it's about stream buffers instead of the actual streams.
Ok, that seems to make sense for your use case, but then it's completely unrelated to file management, and shouldn't even be part of boost::filesystem (but rather boost::iostream).
You're absolutely right about that. I wasn't suggesting what library it should belong to. Regardless, though, the temporary file facilities should be organized together and not strung out over a number of different libraries.
You seem to want a temporary stream (i.e. as you say, something to write into and read from). Does it really matter (for you) whether that is implemented by means of a file ? If so, what observable behavior should it have that makes it file-like ? The subject, however, suggests a temporary file, i.e. an entity in a file system. That, too, is important, as a number of people have confirmed. I don't see much relationship between them, in particular on an API level. Why would you lump them together ? Regards, Stefan