iostream trouble (accessing basic_ios)

[Michael Bruschkewitz]

Hello,
I'm somehow annoyed.

This works:
using namespace std; // <-- Don't like this
std::basic_filebuf<char> fb;
fb.open("out.txt",std::ios_base:ut);
std::basic_ofstream<char> ofs;
ofs.basic_ios<char>::rdbuf(&fb);
This too:
typedef basic_ios<char> bioschar; // Don't like this
ofs.bioschar::rdbuf(&fb);
This not:
// Would like this
std::basic_filebuf<char> fb;
fb.open("out.txt",std::ios_base:ut);
std::basic_ofstream<char> ofs;
ofs.std::basic_ios<char>::rdbuf(&fb); // <-- but Error here

Generally, I don't like using using. I don't like the typedef version
either. Is there an easy way to make the last version working? (MSVC6)

TIA,
Michael B.

 

[SirMike]

Generally, I don't like using using. I don't like the typedef version
either. Is there an easy way to make the last version working? (MSVC6)

I think it is a compiler problem because on MSVC++ .NET2k3 it compiles
without problems.

SirMike

 

[Michael Bruschkewitz]

I think it is a compiler problem because on MSVC++ .NET2k3 it compiles
without problems.

SirMike

So I'll have to deal with it. Thank you for the fast response.

Michael B.

 

[Ron Natalie]

Generally, I don't like using using. I don't like the typedef version
either. Is there an easy way to make the last version working? (MSVC6)

I know VC 6 has som problems with name qualification (for example
using std::vector; vector<int>::iterator x;
yeilds errors as well.

If you don't mind, can I ask what you are atrying to accomplish?
If you're going to manage the stream buffers yourself, why not
use a basic_ostream instead (which doesn't overload the stream
buffer). fstream is unprepared for you to replace the buffer
it created (it assumes that the one it fed to the basic_ios is
the same one that will be there at destruction time).

 

[Chris \( Val \)]

message | In article <[email protected]>, (e-mail address removed)
| says...
| > Michael Bruschkewitz wrote:
| > > Generally, I don't like using using. I don't like the typedef version
| > > either. Is there an easy way to make the last version working? (MSVC6)
| > I think it is a compiler problem because on MSVC++ .NET2k3 it compiles
| > without problems.
| >
| > SirMike
| >
| So I'll have to deal with it. Thank you for the fast response.

It also compiles just fine with 'Borland C++ Builder 5.0 UP-1'.

Cheers.
Chris Val

 

[Michael Bruschkewitz]

If you don't mind, can I ask what you are atrying to accomplish?
If you're going to manage the stream buffers yourself, why not
use a basic_ostream instead (which doesn't overload the stream
buffer). fstream is unprepared for you to replace the buffer
it created (it assumes that the one it fed to the basic_ios is
the same one that will be there at destruction time).

That's an example from Langner/Kreft: Standard C++ IOStreams and
Locales.

I create a outstream which is used for logfiles. These logfiles should
not exceed a certain size. This is done by :
class CLogFileBuf : public std::basic_filebuf<char> ...

CLogFileBuf::int_type CLogFileBuf:verflow(int_type _C)
{ int_type rc = inherited:verflow(_C);
++m_counter;
if(m_counter>=m_maxSize && _C=='\n') opennext();
return rc;
}
void CLogFileBuf:pennext()
{ inherited::close();
m_counter=0;
createNextFn(m_fnTempl,m_fn); // template-name, current name
inherited:pen(m_fn.c_str(),std::ios_base:ut);
}

Maybe I need some cleanup, but until now, it works.

Michael B.