In article <42121e1e@news.povray.org>, war### [at] tagpovrayorg says...
>   While one could call an #include file a "plugin", I would call it
> a library, not a plugin. Even if a future version of POV-Ray with a
> much more elaborated and powerful scripting language (supporting eg.

> not plugins (in the same sense as dll plugins are).
> 
Which makes a lot of sense. And as I mentioned, there is nothing to 
prevent a special directive like <library "name">, to explicitly make it 
not just a simple include, thus allowing it to also be added to a global, 
'allow all scenes access automatically' type feature.

There is no real reason to go for full plugins if the SDL can manage it, 
but some way to explicitly prevent name collisions and allow global use 
'would' be nice. It simplifies usage of any such things a lot.

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message