How can I format stream not in such an awkward way?

[Steven Woody]

Here is the code,

uint16_t n1, n2;
...
std:stringstream os;
os << "(" << std::hex << std::setw(4) << std::setfill('0')
<< n1 << "," << std::setw(4) << std::setfill('0')
<< n2 << ")";

You see, I have to used setw,setfill twice for print two integer.
This is the only we I found works. Is there a simple representaion to
archive same purpose?

Thanks!

-
narke

 

[Michael DOUBEZ]

Steven Woody a écrit :

Here is the code,

uint16_t n1, n2;
...
std:stringstream os;
os << "(" << std::hex << std::setw(4) << std::setfill('0')
<< n1 << "," << std::setw(4) << std::setfill('0')
<< n2 << ")";

You see, I have to used setw,setfill twice for print two integer.
This is the only we I found works. Is there a simple representaion to
archive same purpose?

You don't need the second std::setfill('0') but you need a setw() for
each output concerned.
If you do:
os<<std::setw(4) << std::setfill('0')<<",";
output is '000,'.
os.setf(ios::hex, ios::basefield)
os.fill('0');
os << "("
<< std::setw(4) << n1 << ","
<< std::setw(4) << n2
<< ")";

 

[Steven Woody]

Steven Woody a écrit :




You don't need the second std::setfill('0') but you need a setw() for
each output concerned.
If you do:
os<<std::setw(4) << std::setfill('0')<<",";
output is '000,'.
os.setf(ios::hex, ios::basefield)
os.fill('0');
os << "("
<< std::setw(4) << n1 << ","
<< std::setw(4) << n2
<< ")";

Thank you, I understand.

 

[James Kanze]

Here is the code,

uint16_t n1, n2;
...
std:stringstream os;
os << "(" << std::hex << std::setw(4) << std::setfill('0')
<< n1 << "," << std::setw(4) << std::setfill('0')
<< n2 << ")";

You see, I have to used setw,setfill twice for print two
integer. This is the only we I found works. Is there a
simple representaion to archive same purpose?

os << '(' << HexFmt( 4 ) << n1 << ',' << HexFmt( 4 ) << n2 <<
')' ;

More generally, the standard manipulators (except maybe for
setw) are really only there to serve as examples. You wouldn't
normally use them in real code; you'd define application
specific manipulators, like HexFmt above. (My implementation of
HexFmt is available at my site, but more generally, you'll want
to provide your own, since only you know what logical markup is
applicable to your application.)