i/o Fortran's format commands in c++

[maria]

I 've decided it's time to move from fortran to c++, but i cant find
out if c++ supposrts I/O format commands like the ones in fortran 77.
I would be gratefull for any help.
Thank you

[Jacques Labuschagne]

maria wrote:

I 've decided it's time to move from fortran to c++, but i cant find
out if c++ supposrts I/O format commands like the ones in fortran 77.
I would be gratefull for any help.
Thank you

You assume we know Fortran. Why not describe how the IO should behave
first?

Jacques

[David Harmon]

On 13 Jan 2004 19:40:25 -0800 in comp.lang.c++, ma*****@hotpop. com
(maria) was alleged to have written:

I 've decided it's time to move from fortran to c++, but i cant find
out if c++ supposrts I/O format commands like the ones in fortran 77.

The printf(), scanf(), etc. library functions, that C++ inherits
from C, provide formatted I/O somewhat reminiscent of Fortran formatted
I/O. Most C++ programmers prefer the standard iostreams library for
type safety and extensibility.

See the section "[15] Input/output via <iostream> and <cstdio>" in
Marshall Cline's C++ FAQ. It is always good to check the FAQ before
posting. You can get the FAQ at:
http://www.parashift.com/c++-faq-lite/

[E. Robert Tisdale]

maria wrote:

I 've decided that it's time to move from Fortran to C++
but I can't find out if C++ supports I/O format commands
like the ones in fortran 77.

Why can't you find out?
Do you have a C++ text book?

The C computer programming language has format *strings*
PRINTF(3) Linux Programmer’s Manual PRINTF(3)

NAME
printf, fprintf, sprintf, snprintf, vprintf, vfprintf,
vsprintf, vsnprintf - formatted output conversion

SYNOPSIS
#include <stdio.h>

int printf(const char *format, ...);
int fprintf(FILE *stream, const char *format, ...);
int sprintf(char *str, const char *format, ...);
int snprintf(char *str, size_t size, const char *format, ...);

[Nick Hounsome]

"David Harmon" <so****@netcom. com> wrote in message
news:40******** *******@news.we st.earthlink.ne t...

On 13 Jan 2004 19:40:25 -0800 in comp.lang.c++, ma*****@hotpop. com
(maria) was alleged to have written:

I 've decided it's time to move from fortran to c++, but i cant find
out if c++ supposrts I/O format commands like the ones in fortran 77.
The printf(), scanf(), etc. library functions, that C++ inherits
from C, provide formatted I/O somewhat reminiscent of Fortran formatted
I/O. Most C++ programmers prefer the standard iostreams library for
type safety and extensibility.

Do they really?

I think it depends on what you mean by formatted. Personally I find them
extremely clunky for doing what I usualy think of
as formatted I/O i.e. the difference between 0x%06x and %d.

Putting aside the biggest problem which is properly saving and restoring the
base and fill character, including iomanip,
upper versus lower case hex letters and the std namespace you still have:
cout << x << hex << "0x" << setw(6) << setfill('0') << y << dec;
versus
printf("%d 0x%06x",x,y);

I think that the standard should actualy supply a class to save and restore
all this 'stuff' automatically in ctor/dtor e.g.
std::format_sta te fs(cout);

This is in no way intended to deny that they are wonderful for printing
classes where C has nothing.
See the section "[15] Input/output via <iostream> and <cstdio>" in
Marshall Cline's C++ FAQ. It is always good to check the FAQ before
posting. You can get the FAQ at:
http://www.parashift.com/c++-faq-lite/

[David Harmon]

On Wed, 14 Jan 2004 06:45:06 -0000 in comp.lang.c++, "Nick Hounsome"
<nh***@blueyond er.co.uk> was alleged to have written:

I/O. Most C++ programmers prefer the standard iostreams library for
type safety and extensibility.
Do they really?

Yes.
I think it depends on what you mean by formatted.
Formatted means converted to or from a legible character representation.
printf() and scanf() are formatted. read() and write() are raw or
unformatted. <iostream>'s operator<<() and operator>>() are formatted.
Personally I find them
extremely clunky for doing what I usualy think of
as formatted I/O i.e. the difference between 0x%06x and %d.

Both of those are formatted. Come on, this isn't rocket science.

[Jeff Flinn]

"Nick Hounsome" <nh***@blueyond er.co.uk> wrote in message
news:Hy******** *******@news-binary.blueyond er.co.uk...

"David Harmon" <so****@netcom. com> wrote in message
news:40******** *******@news.we st.earthlink.ne t...

On 13 Jan 2004 19:40:25 -0800 in comp.lang.c++, ma*****@hotpop. com
(maria) was alleged to have written:

I 've decided it's time to move from fortran to c++, but i cant find
out if c++ supposrts I/O format commands like the ones in fortran 77.
The printf(), scanf(), etc. library functions, that C++ inherits
from C, provide formatted I/O somewhat reminiscent of Fortran formatted
I/O. Most C++ programmers prefer the standard iostreams library for
type safety and extensibility.

Do they really?

I think it depends on what you mean by formatted. Personally I find them
extremely clunky for doing what I usualy think of
as formatted I/O i.e. the difference between 0x%06x and %d.

Putting aside the biggest problem which is properly saving and restoring

the base and fill character, including iomanip,
upper versus lower case hex letters and the std namespace you still have:
cout << x << hex << "0x" << setw(6) << setfill('0') << y << dec;
versus
printf("%d 0x%06x",x,y);

I think that the standard should actualy supply a class to save and restore all this 'stuff' automatically in ctor/dtor e.g.
std::format_sta te fs(cout);

See http://www.boost.org/libs/io/doc/ios_state.html which saves the state as
you desire. If you still insist on printf, see
http://www.boost.org/libs/format/index.htm for a typesafe version.

Jeff F

[Nick Hounsome]

"Jeff Flinn" <NO****@nowhere .com> wrote in message
news:bu******** **@bluegill.adi .com...

"Nick Hounsome" <nh***@blueyond er.co.uk> wrote in message
news:Hy******** *******@news-binary.blueyond er.co.uk...

"David Harmon" <so****@netcom. com> wrote in message
news:40******** *******@news.we st.earthlink.ne t...

On 13 Jan 2004 19:40:25 -0800 in comp.lang.c++, ma*****@hotpop. com
(maria) was alleged to have written:
>I 've decided it's time to move from fortran to c++, but i cant find
>out if c++ supposrts I/O format commands like the ones in fortran 77.

The printf(), scanf(), etc. library functions, that C++ inherits
from C, provide formatted I/O somewhat reminiscent of Fortran formatted I/O. Most C++ programmers prefer the standard iostreams library for
type safety and extensibility.

Do they really?

I think it depends on what you mean by formatted. Personally I find them
extremely clunky for doing what I usualy think of
as formatted I/O i.e. the difference between 0x%06x and %d.

Putting aside the biggest problem which is properly saving and restoring

the

base and fill character, including iomanip,
upper versus lower case hex letters and the std namespace you still have: cout << x << hex << "0x" << setw(6) << setfill('0') << y << dec;
versus
printf("%d 0x%06x",x,y);

I think that the standard should actualy supply a class to save and

restore

all this 'stuff' automatically in ctor/dtor e.g.
std::format_sta te fs(cout);

See http://www.boost.org/libs/io/doc/ios_state.html which saves the state

as you desire. If you still insist on printf, see
http://www.boost.org/libs/format/index.htm for a typesafe version.

Jeff F

Great but you will see that I said "I think that the standard should actualy
supply ...."

[Rob Williscroft]

Nick Hounsome wrote in
news:Hy******** *******@news-binary.blueyond er.co.uk:

I think that the standard should actualy supply a class to save and
restore all this 'stuff' automatically in ctor/dtor e.g.
std::format_sta te fs(cout);

void f( int i )
{
std::ostream os( cout.rdbuf() );
os << std::hex << i;
}

Rob.
--
http://www.victim-prime.dsl.pipex.com/

[Jeff Flinn]

....

Putting aside the biggest problem which is properly saving and

restoring the

base and fill character, including iomanip,
upper versus lower case hex letters and the std namespace you still

....

See http://www.boost.org/libs/io/doc/ios_state.html which saves the

state as

you desire. If you still insist on printf, see
http://www.boost.org/libs/format/index.htm for a typesafe version.

Great but you will see that I said "I think that the standard should actualy supply ...."

Considering the large number of facilities from boost that have been
proposed in TR1, perhaps with a little prodding the ios_state could be
proposed for TR2, then your wish could be reality.

Jeff F