[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Make fstream.attach() transparent for big project migration
From: |
Spectre |
Subject: |
Re: Make fstream.attach() transparent for big project migration |
Date: |
12 Jun 2006 06:44:02 -0700 |
User-agent: |
G2/0.2 |
I'll look up the source. It must be somewhere.
Thanks Uli !
Ulrich Eckhardt wrote:
> Spectre wrote:
> > I have a huge c/c++ project from 1992
>
> I.e. pre-standard C++, the C part is much more likely to work unmodified.
>
> > that I have to migrate to GNU GCC 3.4.1. It wants the attach() function
> > of fstream.
>
> The functions of std::fstream are defined by the C++ standard and it
> doesn't have an attach() function.
>
> > Is there a way I can get the project to see the functionality of having
> > the attach() function?
>
> What does it do, attach a FILE* or a filedescriptor? What is its intended
> use? Just as suggestion, take a look at the rdbuf() function of iostreams.
> Other than that, I think GCC's standardlibrary includes
> standard-extensions that ease interaction with above mentioned FILE* and
> filedescriptor.
>
> Be prepared for having to do lots of porting though, quite a few things
> changed before IOStreams were finally standardised.
>
> > Does anyone happen to have the source for that function without 1992
> > dependencies that I could drop into a helper function or something
> > like that.
>
> With what did you compile it up to now? You should look at the current
> compiler's headers to see what this thing is, also, many
> (pre-)standardlibraries come with documentation and at least partially
> sourcecode.
>
> Uli
>
> --
> http://gcc.gnu.org/faq.html
> http://parashift.com/c++-faq-lite/