POV-Ray : Newsgroups : povray.unofficial.patches : #declares and memory management : Re: #declares and memory management Server Time
18 Aug 2024 16:15:10 EDT (-0400)
  Re: #declares and memory management  
From: Warp
Date: 25 May 2001 10:50:28
Message: <3b0e7134@news.povray.org>
Thorsten Froehlich <tho### [at] trfde> wrote:
: I still have tons of such code in my mailbox from people (8-10 of about 30)
: who took an intro to data structures class (I was the teaching assistant)
: and came up with 82 lines and three while-loops (in C) to reverse a doubly
: linked list.  Then there are the "better" solutions that need one while-loop
: and a function that returns the nth element (a second while-loop).  And this
: in university (first year of course) so they were at least told what is
: wrong with their code...

  This is exactly what I meant.

  I don't think it's a very good idea to hurry too much. I know that the
idea of making a POV-Ray patch is exciting, but in the long run too much
hurry causes more problems than it's worth.
  If the goal is to learn programming, there are much better ways of doing
it than go straight to POV-Ray source code and try to understand it. POV-Ray
is huge and made by many people and it uses very complicated algorithms
which are not easy to understand. Trying to deal with all this in a state
where you are still trying to remember how to write a function can be just
too much.

  Of course you can try if you want. Who am I to stop you anyways? I'm just
trying to give advice based on my own experience.

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


Post a reply to this message

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