I too have been trying to build under windows and ran across the same problem with the t variable. Assuming gcc allows it for some reason, by default is_closure() is false so that is what i set it

aaa))))that is sooooo cool))thx) http://gwy.in/jokesoffice

I do a most of my day-to-day development on Snow Leopard, so I know this can be made to work. Are you building OIIO by checking out the "external" project and trying to build the whole thing? If so,

Hi Chris, Thank you very much for your reply. It works! Here comes the next problem compiling the "osllex.cpp" file generated by flex from "osllex.l"

I'm having some difficulty building OpenImageIO on macos (Snow Leopard), as a required pre-requisite for building OSL. The build of the external packages fails because libtiff doesn't build.

The chunk of code between the '{' and '}' is just C++ (mostly, except for the $ markers of course). Looking at this, the line TypeSpec t (simple, t.is_closure()); doesn't make any sense to me,

Hi All, I'm trying to compile the OpenShadingLanguage library under Windows using VisualStudio 2008. I was able to compile the following projects so far: - oslquery - oslinfo There is a

Hi guys, After quite some thought I agree that d/dx mod(x,a) == 1 is about about the best you can do, even though it doesn't make sense at the discontinuity. It is possible to make sense of the

Agreed. You answer seems the most useful one. --jono

Well, there's "math" and then there's "what's useful in shaders." In the strict mathematical sense, the derivative is undefined at the discontinuity (x==d), though you could speak of the limit as you

Well, I'm not sure what to think. The derivatives of mod(x,y) is the same as x most of the time, but at the discontinuity? Not sure what else you could really do since the function isn't

Anybody? -- Larry Gritz l...@...

Well, is Larry's baby. I'm in the group that makes the render using OSL. That's right. Yeah That's more of a question for Larry. I know osl closures are in the roadmap, but he is the one to talk to

Hey Alejandro! Great to hear from you, I had no idea you were involved in this project. I incorrectly interpreted what would actually be given to the renderer, I thought it would be a single

In an effort to keep the mail list free of clutter, I think we're deciding NOT to CC the list on every ticket. Instead, those of you who want to follow the gory details of every ticket and every

Comment #3 on issue 48 by larrygritz: texture() should take optional param for missing texture http://code.google.com/p/openshadinglanguage/issues/detail?id=48 Agreed. After I posted that, I was

Comment #2 on issue 48 by jonogibbs: texture() should take optional param for missing texture http://code.google.com/p/openshadinglanguage/issues/detail?id=48 I would want a separate color per

Now that OSL is open source (congrats!), I recommend using the following guide on crediting patches from non-core developers in log

Updates: Cc: larrygritz Labels: Type-Enhancement Priority-Medium Milestone-20100210 Comment #1 on issue 48 by larrygritz: texture() should take optional param for missing

Status: New Owner: larrygritz CC: os...@... New issue 48 by larrygritz: texture() should take optional param for missing