 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Program ended abnormally on 03/06/2004 19:29, Due to a catastrophic Dan P
error:
> Warp wrote:
>
>> Dan P <dan### [at] yahoo com> wrote:
>
>
> <snip />
>
>> They are not strings. Learn C, will you?
>
>
> You know what? I've decided against doing this port after all. I've got
> other plans. With this kind of attitude, and any of you who think this
> is a way to act as a team, you all can kiss my ass, not just Thorsten.
> The last thing I need is to deal with premadonnas like you.
>
> I'm out.
>
Calm down. Try to get over their tone and listen to their advise, it's usually
pretty good. Warp and Thorsten can be abrasive at times, but that's why we like
'em. ;-)
FWIW, I've suffered worse from Thorsten, and I lived to tell the tale.
--
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/* flabreque */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/* @ */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/* videotron.ca */}camera{orthographic location<6,1.25,-6>look_at a }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
> This: "int i = some_double;" is equivalent to this:
> "int i = int(some_double);".
int i = (int)some_double;
--
http://tth.vaboofer.com/Cette/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40bfb795@news.povray.org> , Warp <war### [at] tagpovrayorg> wrote:
> Dan P <dan### [at] yahoocom> wrote:
>> There's a lot I didn't know about. So, kiss my ass.
>
> When you don't know, the first thing to do is to ask, not to go and
> "fix" someone else's code and make a post with a tone of voice which
> sounds like you know better than the original code and that the current
> code sucks.
>
> So, it should be: "Hey, there's some odd code which I don't understand
> and which looks wrong to me. Is it wrong?" "No." "Ah, ok, never mind."
>
> Not: "Hey, there's some odd code which looks wrong to me so I went
> and fixed it, even though I don't really understand what's going on."
>
> If you don't understand how a code works and why it is done as it is
> done, ask.
Exactly!!!
Thorsten
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40bfb232$1@news.povray.org> , Dan P <dan### [at] yahoocom>
wrote:
> Oh, and if your code was so damn good, TF, it wouldn't have crashed
> using a straight-up clean compile on this OS so step-off.
Given what you have done to the code and probably the makefile, this is
hardly surprising! Get a clue, then start to mess with the source code, not
the other way around. As it stands, you wasted tons of your time to "fix"
something that you simply did not understand.
> Warnings warn you of when your code may behave differently on other OS's
> as well. I'm not saying that is true in this case -- it makes sense not
> to call another function there if we don't have to --
Making fairly random changes all over the code is not the correct approach
to try to fix a problem in a program. A debugger is!
> but I didn't think it was "nonsensical".
It is because you assume you know so much better than the original authors
and that those tens of individuals were all so stupid that we needed you to
come along and fix our code. Did it occur to you that this is not likely?
Thorsten
PS: You are not the first person to not understand what a multicharacter
constant is, it has been discussed in this group before, so I will add a
note to that file to help all those people understand. Never expected
something like this would be necessary <sigh>
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 03 Jun 2004 18:18:00 -0500, Dan P <dan### [at] yahoocom> wrote:
> Right; this is what I expected when I posted to this group. That initial
> post threw me off. I thought maybe you and TF weren't listening. Okay,
> listen; I didn't know about the MultiCharacter constant thing. There's a
> lot I didn't know about. So, kiss my ass.
I think I started at the same point as you so I think I have some reference.
Note, nobody said "kiss our ass if you do not know what multicharacter is." I
didn't know multicharacter issue too when I started reading 3.5 sources. And I
went through fixing warnings too, but I never asked for favour to my ass
because it's clear that before bothering some team about used rules you have
to understand them before you start to fix them. Even unofficial port is not
welcome by community if it is done wrong, that's clear. There _is_ experience
in POV Team Members, think about them like about teachers. You ask teacher:
"hello, I want to make another unofficial nuclear power plant by playing with
atoms in my room". Teacher answer "Doing it this way is wrong and it's
illegal, there are some rights and conventions. My brain is hurt because of
your will". "Then kiss my ass" you answer to your teacher. Childish.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> So, it should be: "Hey, there's some odd code which I don't understand
> and which looks wrong to me. Is it wrong?" "No." "Ah, ok, never mind."
Maybe the usual problem in such cases is the staight "No." answer.
Giving a slightly more informative answer could in the end save a lot of
time, which is otherwise "wasted" answering complaints as in this thread.
Well, I also know that time is precious, especially at the moment.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thierry Boudet <oul### [at] chezcom> wrote:
> > "int i = int(some_double);".
> int i = (int)some_double;
Well, POV-Ray is compiled with a C++ compiler currently. May as well use
the C++ way.
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet <pov### [at] freefr> wrote:
> Maybe the usual problem in such cases is the staight "No." answer.
That "No." was only symbolic, for shortness. Of course it meant a
proper negative answer.
--
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
>>>"int i = int(some_double);".
>
>> int i = (int)some_double;
>
> Well, POV-Ray is compiled with a C++ compiler currently. May as well use
> the C++ way.
>
Ah OK, sorry. I'm not a C++ expert, I'm to old for this modern
technology :)
--
http://tth.vaboofer.com/Cette/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thierry Boudet <oul### [at] chezcom> wrote:
> > Well, POV-Ray is compiled with a C++ compiler currently. May as well use
> > the C++ way.
> >
> Ah OK, sorry. I'm not a C++ expert, I'm to old for this modern
> technology :)
There's a reason for the new syntax. It has to do with abstract types
(classes and template parameters). However, I don't think anyone is
interested in another C++ lecture of mine... :P
--
#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
|
|
| |
| |
|
|
|
|
| |
|
|
