search for: asmstreambuf

.... Slowness of std::cout and friends due to their reliance on FILE * buffering and resulting excessive virtual function calls. I just implemented "standard" AsmStreams (the name for my custom streams) to handle the cases where we want to dump Asm to standard error. I just point the AsmStreambuf to STDERR_FILENO. I simply avoid the constructor issue by declaring that no user shall write to an AsmStream in a static object constructor. So we don't have worries about multiple constructor calls at program startup. There is no ios_base::Init equivalent for AsmStream. The second conce...

On Fri, 17 Aug 2007, David Greene wrote: >> Posix is pretty available, what system doesn't have them? > > Windows, for one. If POSIX is ok, it's better in my mind to just directly Windows has POSIX calls. > use open, write and friends, which is what I do now. Going the cstdio > route should only be done for portability reasons to support non-POSIX > systems. I

...buffering and resulting excessive virtual function calls. Use of FILE* is not the issue, virtual functions are. > I just implemented "standard" AsmStreams (the name for my custom streams) to > handle the cases where we want to dump Asm to standard error. I just point > the AsmStreambuf to STDERR_FILENO. I simply avoid the constructor issue by > declaring that no user shall write to an AsmStream in a static object > constructor. So we don't have worries about multiple constructor calls at > program startup. There is no ios_base::Init equivalent for AsmStream. This...