Michał Król | 3 Apr 2006 10:23
Picon

Re: GLSL preprocessor status

On 02/04/06, Jeffrey Timanus <timanuj <at> discreet.com> wrote:
>
> Hi Michal,
>
> I've unfortunately had little spare time to pour into my pre-processor
> project lately.
>
> If I really find time for the project, I should be able to have a working
> version in 4 weeks.  I'm planning on trying to spend more time on my hobby
> coding . . but we all know how difficult that can become.
>
It will be just fine if the preprocessor is included in the next,
stable release.
In the 4 weeks I am planning to finish things that are more important than
the preprocessor, just that.

> I must admit, I haven't looked at your parser very recently.  One issue
> I'm looking at for my work is to allow the system to support arbitrary
> re-winding of the stream in the case of parser errors or lexical
> ambiguities.  Does your parser require the need to rewind the stream at
> all during error recovery?
>
You dont have to look at the parser. The GLSL specification makes it
possible to separate preprocessor part from the syntax parser part.
I just need a function that takes raw shader source and returns either
error condiftion with message and line number, or fully preprocessed
source with a table that maps line numbers to character positions
in the returned string.

--
(Continue reading)


Gmane