LGTM http://codereview.appspot.com/189060

Reviewers: , Message: Review at http://codereview.appspot.com/189060 Description: Bug introduced with r507 when I overhauled compound initializers in ASTvariable_declaration. Forgot one place where

We're big fans of code reviews BEFORE committing into the trunk, and at SPI used ReviewBoard religiously while developing OSL. We're still trying to figure out how to do reviews the way we prefer,

still getting the fails, If I do a make debug I get loads of boost Undefined symbols: errors (for example) Linking CXX shared library liboslexec.dylib Undefined symbols:

The "run.py" script takes arguments (which are passed when the testsuite is run). You want: cd testsuite/YOURTEST ./run.py . ../../build/ARCH (ARCH in your case is "macosx") Does that help? If

I've just run it in gdb and got the following Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000001 0x0016a07d in

Building on Mac OS X (Darwin) seems to work and run but when I try most of the tests it seems to fail with a bus error For example (geomath) edit run.py to work with my local

Aha, you must be a prior OpenImageIO user. You need to 'svn update' and recompile your OIIO -- this code in OSL requires a recent change to the ParamValueList helper class that's part of OIIO. At

Hi, I encountered several minor build errors both on release and debug. I corrected a few (I'll release a patch if you're interrested) but there is one i can't explain

I've posted a Wiki page giving a brief introduction to the project, a list of things unique to OSL (compared to other shading languages), a status report on the current state of the project. Click on

OK, it seems to have been synced. The trunk is now where we're actually doing all our development. We will periodically make release branches and tags at stable points. -- lg

Whoops, I see what I did. Thanks David

http://code.google.com/p/openshadinglanguage/downloads/list wrote:

Am I blind? If I click on "Files" I don't see any files listed. There is also no downloads link.

On the "downloads" tab.

The code is syncing right now, revision by revision. But it's going to take an hour or two before it's caught up. So don't bother checking out the code until I send out the email letting

Nice! I can't wait to start playin with the code.

We are in the process of moving OSL's full source code to googlecode. Right now. This is not just a snapshot. It's our live development trunk for the OSL software we are using at SPI, and from today

The whole thing will be up very soon. Days. Stay tuned. -- lg

Hi Larry - Hope your deadlines went okay. Any news on when a preliminary spec will be available? Thanks, Brian