------- Comment #4 from pcarlini at suse dot de 2006-04-19 16:38 -------
(In reply to comment #3)
> 1.
> Agree, I wouldn't call it a bug. But I don't know where to put it other than
> here.
Maybe report it to Sun?
> 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.
Therefore, by definition, the fopen "simulation" which uses open doesn't behave
"as-is" fopen were called...
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?
I don't think so, because in the past we resisted many times putting (ugly)
workarounds for specific limitations of some targets. Also, storing an int
instead of a FILE* would certainly break the binary compatibility. I can leave
this open, as an enhancement, but I'm afraid that we are not going to make any
kind of progress on it for a long time...
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27198
