John VanSickle <evi### [at] hotmailcom> wrote:
> How hard would it be to separate the parser and the renderer as much as 
> possible, and thereby allow for both a parser based on the current SDL, 
> and another parser based on an entirely different SDL (as well as a 
> rendering engine that is not primarily a ray-tracer)?

  I'm not 100% sure that separating the parser from the renderer even
further is actually the right thing to do.

  It may sound rational because it would allow changing the parser easily.

  However, that's where the advantages end. The disadvantage is, however,
that it would limit the usability of the language *during rendering* even
more than the current SDL (which at least has user-defined functions which
can be evaluated during render-time).

  A separate "shader" language and a "post-processing" language would be
needed for enhanced functionality. That's already three separate languages
in one. Is that really what we want? Or do we want one language which can
be used for everything?

-- 
                                                          - Warp

Post a reply to this message