Re: [Stlport-devel] [Stlport-cvs] SF.net SVN: stlport:[3611] trunk/STLport

[François D. <fra...@fr...>]

    I didn't had a lot of answer to my clc++m request:

http://groups.google.com/group/comp.lang.c++.moderated/browse_thread/thread/c235ca48af945aa6/54c796e6a5dfe58e?lnk=gst&q=ios_base#54c796e6a5dfe58e

    It simply looks like no one consider it as a problem. According the 
result neither C nor C++ Standard are saying what should be file pointer 
position once a file is open with fopen with "a" mode or ofstream with 
ios_base::app. So modification in fstream_unix.cpp is not wrong but 
simply useless or even redundant with file position that will take place 
on the first write operation.

    Whatever, Petr had already close the debate by closing my SVN write 
access (Boris Fomitchev one too!). I considered that it was the good 
moment to leave STLport project. My only regret is that I won't have had 
the time to do the 5.2 release, not sure Petr will take care of it as he 
considered it as a "marketing release" when I proposed it. So do not 
hesitate to submit your patch on sourceforge patch tracker, I hope Petr 
will apply it.

Bests

Ulrich Eckhardt wrote:
> Guys, the issue with the fstream behaviour is still waiting for a resolution. 
> Apart from several misunderstandings, are there still technical differences? 
> Further, is there anything that should keep us from releasing 5.2.0 or 
> another 5.1.x?
>
> Petr, are you planning to implement support for the upcoming draft C++ 
> standard in a separate branch or via preprocessor? As far as I'm concerned, 
> I'd rather not have this feature included into the upcoming 5.2 yet, at least 
> not by default.
>
> BTW: I'm currently trying to get STLport to compile against an MS Windows CE6 
> SDK using VC8, expect some patches in the next few days!
>
> cheers!
>
> Uli
>
>