POV-Ray : Newsgroups : povray.general : pov source gcc3 problem Server Time
18 Nov 2024 15:21:31 EST (-0500)
  pov source gcc3 problem (Message 1 to 10 of 29)  
Goto Latest 10 Messages Next 10 Messages >>>
From: Christian Parpart
Subject: pov source gcc3 problem
Date: 1 Aug 2002 19:59:28
Message: <3d49cb5f@news.povray.org>
HI all,

well, that's the time where I hate my fucking new system :(sorry:)
But it is as it is. I can't just unzip configur and compile the sources 
because of some basic C++ standard issues. such as max and std::max. gcc 
has been very loosely to the ANSI/ISO C++ standard in gcc 2.x. Most of 
these issues has been fixed now and, what's now? lots of sources (such as 
povray) can't be compiled.

That's now good :(

Will the developer fix that? or do we need to walk through the code and add 
the namespace prefix (std::) to each standard function? This wouldn't be 
nice since I'm pretty sure that I'm not the only one who should do exactly 
the same as the others in that case.

Thanks,
Christian Parpart.


Post a reply to this message

From: Steve
Subject: Re: pov source gcc3 problem
Date: 1 Aug 2002 20:40:30
Message: <slrnakjl7j.hmh.steve@zeropps.org.uk>
On Fri, 02 Aug 2002 01:59:28 +0200, Christian Parpart wrote:
> HI all,
> 
> well, that's the time where I hate my fucking new system :(sorry:)

No need to be sorry just don't swear it's that simple. 
 
> Will the developer fix that? or do we need to walk through the code and add 
> the namespace prefix (std::) to each standard function? This wouldn't be 
> nice since I'm pretty sure that I'm not the only one who should do exactly 
> the same as the others in that case.

Have a look around in some other groups that you think may contain the 
answer to your question, it so happens that your question was answered
some hours ago in povray.unix.  

-- 
%HAV-A-NICEDAY                    email mailto:ste### [at] zeroppsuklinuxnet
Steve                                web http://www.zeropps.uklinux.net/
                                             or http://start.at/zero-pps
  1:35am  up 35 days, 11:57,  1 user,  load average: 1.29, 1.24, 1.21


Post a reply to this message

From: Warp
Subject: Re: pov source gcc3 problem
Date: 1 Aug 2002 21:59:54
Message: <3d49e79a@news.povray.org>
Quick fix: Add 'using namespace std;' to config.h
  (Ugly perhaps, but who cares? At least it compiles.)

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -


Post a reply to this message

From: Tony[B]
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 08:53:53
Message: <3d4a80e1@news.povray.org>
>   Quick fix: Add 'using namespace std;' to config.h
>   (Ugly perhaps, but who cares? At least it compiles.)

I have no problem with it, but I do remember you going on about how it isn't
something you should grow accustomed to doing. I'm surprised you're the one
suggesting it. :)


Post a reply to this message

From: Christian Parpart
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 09:21:50
Message: <3d4a876e@news.povray.org>
Warp inspired the electrons to say:
>   Quick fix: Add 'using namespace std;' to config.h
>   (Ugly perhaps, but who cares? At least it compiles.)

Exactly. That's what I did. Quick'n'dirty.
And, as we was talking in povray.unix group about too (unfortunately).

Greets,
christian.


Post a reply to this message

From: Bob Jamison
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 17:25:38
Message: <3D4AF8A0.3050100@lincom-asg.com>
Christian Parpart wrote:
> HI all,
> 
> well, that's the time where I hate my fucking new system :(sorry:)
> But it is as it is. I can't just unzip configur and compile the sources 
> because of some basic C++ standard issues. such as max and std::max. gcc 
> has been very loosely to the ANSI/ISO C++ standard in gcc 2.x. Most of 
> these issues has been fixed now and, what's now? lots of sources (such as 
> povray) can't be compiled.
> 
> That's now good :(
> 
> Will the developer fix that? or do we need to walk through the code and add 
> the namespace prefix (std::) to each standard function? This wouldn't be 
> nice since I'm pretty sure that I'm not the only one who should do exactly 
> the same as the others in that case.
> 
> Thanks,
> Christian Parpart.


Christian,

This simple thing works until that issue is fixed.
Put these lines in config.h:


#ifndef max
#define max(a,b) ( a > b ? a : b )
#endif
#ifndef min
#define min(a,b) ( a < b ? a : b )
#endif



This is easier than searching & prefacing all max
and min calls with std:: ,  eh?   ;-)





Bob Jamison
LinCom Corp


Post a reply to this message

From: Warp
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 20:34:28
Message: <3d4b2513@news.povray.org>
Bob Jamison <rja### [at] lincom-asgcom> wrote:
> #ifndef max
> #define max(a,b) ( a > b ? a : b )
> #endif
> #ifndef min
> #define min(a,b) ( a < b ? a : b )
> #endif

> This is easier than searching & prefacing all max
> and min calls with std:: ,  eh?   ;-)

  How is it easier than writing 'using namespace std;' instead?

  Besides, your solution is very bad. Do you know why?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

From: Ron Parker
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 21:52:29
Message: <slrnakmdr0.p47.ron.parker@fwi.com>
On 2 Aug 2002 20:34:28 -0400, Warp wrote:
> Bob Jamison <rja### [at] lincom-asgcom> wrote:
>> #ifndef max
>> #define max(a,b) ( a > b ? a : b )
>> #endif
>> #ifndef min
>> #define min(a,b) ( a < b ? a : b )
>> #endif
> 
>> This is easier than searching & prefacing all max
>> and min calls with std:: ,  eh?   ;-)
> 
>   How is it easier than writing 'using namespace std;' instead?
> 
>   Besides, your solution is very bad. Do you know why?

Oooh!  Oooh!  I know!  I know!

-- 
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}


Post a reply to this message

From: Warp
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 22:11:13
Message: <3d4b3bc1@news.povray.org>
Ron Parker <ron### [at] povrayorg> wrote:
> Oooh!  Oooh!  I know!  I know!

  But you are a professional. You can't participate. ;)

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

From: Rafal 'Raf256' Maj
Subject: Re: pov source gcc3 problem
Date: 2 Aug 2002 23:02:01
Message: <Xns925F329772CB7raf256com@204.213.191.226>
Warp <war### [at] tagpovrayorg> wrote in news:3d4b2513@news.povray.org

>> #ifndef max
>> #define max(a,b) ( a > b ? a : b )
>> #endif
>> #ifndef min
>> #define min(a,b) ( a < b ? a : b )
>> #endif

>> This is easier than searching & prefacing all max
>> and min calls with std:: ,  eh?   ;-)
>   How is it easier than writing 'using namespace std;' instead?
>   Besides, your solution is very bad. Do you know why?

<rot13>
fbzr rkcerfvbaf jvyy abg or pnyphyngrq ng pbzcvyr-gvzr ?

-- 
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M


Post a reply to this message

Goto Latest 10 Messages Next 10 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.