 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Over in p.u.p a while back there were a couple of posts regarding POV
v4.0 and the STL - basically the message was that, due to the inconsistency
in the various compiler providers STL implementations, one would not be able
to use the STL within the POV 4.0 source code.
So, why not use a cross-platform STL implementation ?
See : http://www.stlport.org
Supported compilers (taken from website) :
- SUN Workshop C++ Compilers 4.0.x-5.0, 6.0EA, for Solaris
- GNU GCC 2.7.2-2.95 Compilers, for all GCC platforms
- IBM xlC 3.1.4.0, for AIX
- IBM OS/390 C/C++ 1.x - 2.x Compiler, for OS/390 (STLport is the
only available and official ANSI library for this platform)
- IBM VisualAge/ILE C++ for AS/400 Version 4 Release 4, for AS/400
- IBM Visual Age C++ 3.x, for OS/2 and Win32
- HP ANSI C++ Compiler, for HP-UX
- SGI MIPSpro C++ 7.x, for IRIX
- SGI MIPSpro C++ 4.0, for IRIX
- DEC C++ V5.5-004, V6.x for OSF 3.2/4.0, for Digital Unix.
- Tandem NCC, for Tandem OS
- SCO UDK C++, for UnixWare
- Apogee C++ 4.0, for SUN Solaris
- KAI C++ 3.1c, for all KAI platforms
- Portland Group C++ compiler ( pgCC), for all pgCC platforms
- Microsoft Visual C++ 4.x - 6.x, for Win32
- Borland C++ 5.02-5.5, for Win16/32
- Metrowerks CodeWarrior Pro 1.8-5.3, for MacOS, Win32
- Intel (R) C++ 4.0 Reference Compiler, for Win32
- Watcom C++ 10.x-11.0, for DOS, Win16, Win32
- Powersoft's Power++ 2.0, for Win32
- Symantec C++ 7x/8.x, for MacOS and Win32
- Apple MPW and MRC compilers, for MacOS
--
Scott Hill
Software Engineer.
NC Graphics (Cambridge) Ltd.
Web : http://www.ncgraphics.co.uk
E-mail : sco### [at] ncgraphics net
ICQ : 110661991
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Supported compilers (taken from website) :
any free for dos ?
any one for amiga ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Wlodzimierz ABX Skiba" <abx### [at] abxartpl> wrote in message
news:3aa50f00@news.povray.org...
> > Supported compilers (taken from website) :
>
> any free for dos ?
Free no, but MSVC, and probably Borland and Watcom, will target DOS.
> any one for amiga ?
>
Are there any C++ compilers _at all_ for the Amiga ?
--
Scott Hill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 6 Mar 2001 17:20:34 -0000, Scott Hill wrote:
>"Wlodzimierz ABX Skiba" <abx### [at] abxartpl> wrote in message
>news:3aa50f00@news.povray.org...
>> > Supported compilers (taken from website) :
>>
>> any free for dos ?
>
> Free no, but MSVC, and probably Borland and Watcom, will target DOS.
Not MSVC in any recent version. I think v. 1.52 was the last version to target
anything that isn't 32-bit.
>> any one for amiga ?
>
> Are there any C++ compilers _at all_ for the Amiga ?
Well, there's GCC. That works for DOS, too, in the form of DJGPP.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3aa508f0@news.povray.org> , "Scott Hill"
<sco### [at] ncgraphicsnet> wrote:
I apologize in advance for my very clear words. They are not personal.
Please don't be offended.
> So, why not use a cross-platform STL implementation ?
>
> See : http://www.stlport.org
You are missing the point. The point is not having to _deal_ with the
hassle of incompatible STLs. Limiting to a specific implementation that
works on a subset of compilers is by no means a solution to the problem.
The goal is not writing a program using STL but writing a ray-tracer,
thus we need tools that work _flawlessly_ not not those one first has to
fight with for days to know their limitations.
> - SUN Workshop C++ Compilers 4.0.x-5.0, 6.0EA, for Solaris
> - GNU GCC 2.7.2-2.95 Compilers, for all GCC platforms
> - IBM xlC 3.1.4.0, for AIX
> - IBM OS/390 C/C++ 1.x - 2.x Compiler, for OS/390 (STLport is the
> only available and official ANSI library for this platform)
> - IBM VisualAge/ILE C++ for AS/400 Version 4 Release 4, for AS/400
> - IBM Visual Age C++ 3.x, for OS/2 and Win32
> - HP ANSI C++ Compiler, for HP-UX
> - SGI MIPSpro C++ 7.x, for IRIX
> - SGI MIPSpro C++ 4.0, for IRIX
> - DEC C++ V5.5-004, V6.x for OSF 3.2/4.0, for Digital Unix.
> - Tandem NCC, for Tandem OS
> - SCO UDK C++, for UnixWare
> - Apogee C++ 4.0, for SUN Solaris
> - KAI C++ 3.1c, for all KAI platforms
> - Portland Group C++ compiler ( pgCC), for all pgCC platforms
> - Microsoft Visual C++ 4.x - 6.x, for Win32
> - Borland C++ 5.02-5.5, for Win16/32
> - Metrowerks CodeWarrior Pro 1.8-5.3, for MacOS, Win32
> - Intel (R) C++ 4.0 Reference Compiler, for Win32
> - Watcom C++ 10.x-11.0, for DOS, Win16, Win32
> - Powersoft's Power++ 2.0, for Win32
> - Symantec C++ 7x/8.x, for MacOS and Win32
> - Apple MPW and MRC compilers, for MacOS
Half of the compilers on this list are not even _able_ to support STL.
Why? Some of them don't support templates (like gcc 2.7.2 or MrC 3.x or
VC 4.x or Symantec C++, which has not been updated for more than four
years at least on the Mac) in any way even close to any pre-standard.
The very fact that this STL had to be "ported" shows that it is a single
big hack, no a usable piece of software. Being able to compile code
does not imply that it is fit for any purpose...
> basically the message was that, due to the inconsistency
> in the various compiler providers STL implementations, one would not be able
> to use the STL within the POV 4.0 source code.
No, you misunderstood.
Last but not least, do not worry about this issue. The team will find a
working compromise, but as pointed out in previous posts about 4.0:
There is no point discussing 4.0 features because nothing has been
decided yet. Do don't spend your time on things that are not needed.
The world is full of interesting and more rewarding problems seeking a
solution. Or, if you have a lot of time, just enjoy ray-tracing :-)
Thorsten
NOTE: Opinions expressed are my own and do not necessarily reflect those
of the POV-Team.
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote in message ...
> Well, there's GCC. That works for DOS, too, in the form of DJGPP.
But on the list was "GNU GCC 2.7.2-2.95 Compilers, for all GCC platforms" -
DJGPP has lower number of version and therefore my question. I think there
wasn't any update in DJGPP long time and perhaps it is not compatible with GCC
2.7.2. The same problem cuold be on Amiga platform.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Scott Hill wrote in message <3aa51c92@news.povray.org>...
>"Wlodzimierz ABX Skiba" <abx### [at] abxartpl> wrote in message
>news:3aa50f00@news.povray.org...
> > > Supported compilers (taken from website) :
> > any free for dos ?
> Free no, but MSVC, and probably Borland and Watcom, will target DOS.
Couldn't this stop a little development of patches for future POV?
There is many authors working on windows with free compilers.
Why to play with free POV should I buy compiler?
> > any one for amiga ?
> Are there any C++ compilers _at all_ for the Amiga ?
http://ftp.wustl.edu/~aminet/dirs/dev_c.html
http://ftp.wustl.edu/~aminet/dirs/dev_gcc.html
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote in message <3aa55da0$1@news.povray.org>...
>Last but not least, do not worry about this issue. The team will find a
>working compromise....
Ahhh, now I feel better. It is reassuring to know that there is a team who
always knows the right answer....
Alessandro Coppo
a.c### [at] iolit
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Having worked on producing such a cross-platform STL a few years ago, I can
tell you that they are loaded with work-arounds, brittle, less than fully
featured, and still make the compiler choke sometimes.
Before adopting one, make sure it has enough functionality to really be
worth the point -- if all you need are a few containers and basic iterators,
(1) it shouldn't be a big deal and (2) STL might be overkill.
Even then, for example with the Microsoft compiler (ships with a customized
version of Plauger's library) it still blows up at seemingly random times.
Can't make collection of some class or another, can't do this, can't do
that, ... just brittle and a headache.
--John
"Scott Hill" <sco### [at] ncgraphicsnet> wrote in message
news:3aa508f0@news.povray.org...
> Over in p.u.p a while back there were a couple of posts regarding POV
> v4.0 and the STL - basically the message was that, due to the
inconsistency
> in the various compiler providers STL implementations, one would not be
able
> to use the STL within the POV 4.0 source code.
> So, why not use a cross-platform STL implementation ?
>
> See : http://www.stlport.org
>
> Supported compilers (taken from website) :
>
> - SUN Workshop C++ Compilers 4.0.x-5.0, 6.0EA, for Solaris
> - GNU GCC 2.7.2-2.95 Compilers, for all GCC platforms
> - IBM xlC 3.1.4.0, for AIX
> - IBM OS/390 C/C++ 1.x - 2.x Compiler, for OS/390 (STLport is the
> only available and official ANSI library for this platform)
> - IBM VisualAge/ILE C++ for AS/400 Version 4 Release 4, for AS/400
> - IBM Visual Age C++ 3.x, for OS/2 and Win32
> - HP ANSI C++ Compiler, for HP-UX
> - SGI MIPSpro C++ 7.x, for IRIX
> - SGI MIPSpro C++ 4.0, for IRIX
> - DEC C++ V5.5-004, V6.x for OSF 3.2/4.0, for Digital Unix.
> - Tandem NCC, for Tandem OS
> - SCO UDK C++, for UnixWare
> - Apogee C++ 4.0, for SUN Solaris
> - KAI C++ 3.1c, for all KAI platforms
> - Portland Group C++ compiler ( pgCC), for all pgCC platforms
> - Microsoft Visual C++ 4.x - 6.x, for Win32
> - Borland C++ 5.02-5.5, for Win16/32
> - Metrowerks CodeWarrior Pro 1.8-5.3, for MacOS, Win32
> - Intel (R) C++ 4.0 Reference Compiler, for Win32
> - Watcom C++ 10.x-11.0, for DOS, Win16, Win32
> - Powersoft's Power++ 2.0, for Win32
> - Symantec C++ 7x/8.x, for MacOS and Win32
> - Apple MPW and MRC compilers, for MacOS
>
> --
> Scott Hill
> Software Engineer.
> NC Graphics (Cambridge) Ltd.
> Web : http://www.ncgraphics.co.uk
> E-mail : sco### [at] ncgraphicsnet
> ICQ : 110661991
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I consult for living and I use the SGI STL (v 3.2).
Just to give you the idea, STL is employed in production software by my
largest client, which is a survellilance systems firm (Guyana ESA space
center is monitored by their equipment...).
SGI STL compiles and works correctly even with that pile of brown stuff (tm)
called MSVC++ 6.
If you stay clear from the most "exotic" parts (i.e. partial template
specialization) and do not rely upon the compiler to handle correctly
namespaces (do not write min, write std::min even if you have a using
namespace std;, redundant but harmless), everything is OK, at least for the
needs of a "normal" applications.
I have not tried STLPort, but as it is derived from SGI STL, I expect it to
be almost straight forward to use.
Alessandro Coppo
a.c### [at] iolit
P.S.: if "The Team" starts rewriting collections and so from scratch, my
prediction of 3.5 out for 4Q2001 is too optimistic by at least 6 months ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
