Re: Documentation issues

Paul Miller <pa...@...>

On 6/11/2012 12:03 PM, Jeremy Selan wrote:
Good idea. I'll make a runtime button to switch between the two. That
will also let us confirm the two code paths give similar results. ;)
I just got out of a bad relationship with some code that was handed to me that was full of #ifdefs, so I thought I'd try to do a solid for everyone else and recommend against them. :-)

On Mon, Jun 11, 2012 at 9:43 AM, Paul Miller<pa...@...> wrote:
On 6/11/2012 11:36 AM, Jeremy Selan wrote:


Sorry you're having trouble with the documentation. Which specific
file or url are you at? I'd like to update it to make sure it's

I'd recommend looking into src/apps/ociodisplay/main.cpp

Even though that's a GPU example, 95% of the code would be unchanged
even if we were to use the CPU pathway. (Actually, maybe I should
have ifdef's for CPU vs GPU? It's a nice example.

If you can, make it switchable between the two during run-time, or as a
command-line switch. #ifdefs make the code harder to read.

Join { to automatically receive all group messages.