quote:This is not true. It depends totally on implementation. A poor implementation of iostream will be slow, but a good implementation should be just as fast c''s io.
This may be so, but every iostream implementation I''ve used must be poor because I''ve never seen a quick one.
I assume that the various *nix have asycronous IO (I know Windows does), so that''d be the route I''d suggest for performance. It can be made portable with an abstract factory. But that''s alot of work. If you want quick&easy binary IO, fopen/fclose are your friends.
You should have classes and/or methods that perform the file IO, and they could/should provide exception safety and any other OO features you want.
Magmai Kai Holmlor - Not For Rent
- The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted.-- Tajima & Matsubara