Darren New <dne### [at] sanrrcom> wrote:
> or POV-Ray is too 
> complicated to figure out how to fit plug-ins into it.

  No, I didn't say that.

  I said that there's such a huge amount of little features in POV-Ray
that trying to support replacing/enhancing them through dll plugins is
just not feasible. I didn't say anything about figuring out how to
fit the plugins into it.

> All of *those* 
> arguments are bogus, and I think what I've been seeing here is people 
> shooting down the arguments in *this* paragraph, and not the 
> non-technical reasons above. :-)

  Yet you have still failed to give a description of which features
in the POV-Ray code should call a function implementable in a dll
plugin and what would that plugin do.
  You are still talking as if plugins were some magical code which
could be inserted anywhere and replace anything in the POV-Ray binary.
They simply don't work like that: You have to explicitly code in the
core the plugin calls, and that's my question: Where should POV-Ray
call the plugin and which features should be reimplementable with
the plugin?

-- 
#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