------- Comment #3 from zhong dot xie at yahoo dot ca 2006-04-19 16:08 ------- 1. Agree, I wouldn't call it a bug. But I don't know where to put it other than here.
2. I don't think you have to use fopen for fstream defined by the C++ standard.(see the details below) 3. It is solaris itself limits the fopen to [0,255], which is not a bug either( ANSI C standard). However solaris like other *nix also provide the "open" system call, which can overcome this limit.There are other stdc++ libs r compiler handle this with "open" nicely i.e stlport. As a mulit-platform compiler. Do you think g++ should be able to cover this? Here is What I can see from standard. 27.8.1.3 Member functions [lib.filebuf.members] bool is_open() const; Returns: true if a previous call to open succeeded (returned a non-null value) and there has been no intervening call to close. basic_filebuf<charT,traits>* open( const char* s, ios_base::openmode mode ); Effects: If is_open() != false, returns a null pointer. Otherwise, initial- izes the filebuf as required. It then opens a file, if possible, whose name is the NTBS s (``as if'' by calling ::fopen(s,modstr)). //doesn't mean you have to use fopen. -- zhong dot xie at yahoo dot ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27198