iostreams initialization in Performer 2.0 MR

New Message Reply Date view Thread view Subject view Author view

Randy Stiles (stiles++at++aic.lockheed.com)
Thu, 11 Jan 96 13:05:48 PST

Hi,

This message is concerned with use of iostreams (C++) with Performer
2.0.

I seem to remember some messages on info-performer regarding this
before, but I may have removed them. They mentioned iostreams as
multi-process unsafe, etc. though this hasn't been a problem before.

In our latest port to the final (MR) performer 2.0, it bombs whenever
it encounters uses of iostreams (cout, cerr).

In our previous ports using performer beta 2.0, we did not encounter
this problem.

What is the recommned way to initalize the iostreams package using
Performer 2.0? Is it safe to initialize them, and where is
appropriate, i.e. before pfConfig(), after, etc.

For reference, the main and other top-level source code is compiled
with C++, which usually handles iostream initialization transparently.

-Randy

// Randy Stiles stiles++at++aic.lockheed.com Orgn 9620 Bldg 255
// 415.354.5256 fax: 415.354.5235 3251 Hanover Street
// Lockheed Martin Palo Alto Research Labs Palo Alto, CA 94304-1191
// http://vet.parl.com/~vet/people/stiles/

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:15 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.