2011/4/10 Kai Tietz <[email protected]>
> 2011/4/10 Ruben Van Boxem <[email protected]>:
> > Op 10 apr. 2011 08:49 schreef "Kai Tietz" <[email protected]> het
> > volgende:
> >
> >>
> >> 2011/4/10 James K Beard <[email protected]>:
> >> > JonY - well, mine is in Fortran 95 structured format, with layers of
> >> > classes
> >> > and derived data types. An experienced programmer could port it to
> C++
> >> > fairly quickly, giving you a a C++ class with overloaded arithmetic
> and
> >> > casting/data conversion operations. But I'm not a C++ programmer and
> >> > don't
> >> > want to become one; I'm not in software or computer science and have
> >> > other
> >> > plans for my time than gaining expertise in C++. But I would be happy
> >> > to
> >> > support other people to do the conversion to C++.
> >>
> >> Well, C++ is a good language, but nevertheless for a C runtime-library
> >> something not really usable. At least not for gcc, where we end then
> >> in egg/chicken situation, as initial bootstrap provides C compiler,
> >> but C++ isn't present completely. So if we include a dfp library into
> >> runtime, it needs to be written in C language. But well, to
> >> transscript C++ to C isn't a hard thing. So as startup version a C++
> >> variant might be good enought here.
> >
> > GCC has been working toward having itself compiled by a C++ compiler,
> > partially brought on by ppl/cloog dependencies. It can be enabled as an
> > experimental feature already. Also; a full in-tree build of GCC with c++
> > dependencies (ppl/cloog) is already possible (using host libstdc++) and
> > works at least on Linux. Bootstrapping C++ isn't as impossible as it
> seems
> > with GCC.
>
> Yes, this might be true. But this still doesn't mean that by this
> 128-bit floating points are usable in a general way. There is the
> libquad library in gcc for fortran, which might be the better choice
> here. But this library is LGPLed, which means you - as user - can use
> it only as DLL version and not as static library. So this makes it
> use in our runtime impossible, as we want to provide to our users the
> freedom to use our runtime also in non-GPLed context. Btw same applies
> to Cloog & co, too. So if user wants to use it, well he can do so. But
> we don't dependent on them.
>
> Regards,
> Kai
>
I understand. The point I was making is that it is far from impossible to
include a C++-based mingw-w64 "runtime" library through the GCC build
process.
Ruben
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
