Skip to content

OSLQuery improvements#821

Merged
lgritz merged 1 commit intoAcademySoftwareFoundation:masterfrom
lgritz:lg-oslquery
Nov 28, 2017
Merged

OSLQuery improvements#821
lgritz merged 1 commit intoAcademySoftwareFoundation:masterfrom
lgritz:lg-oslquery

Conversation

@lgritz
Copy link
Copy Markdown
Collaborator

@lgritz lgritz commented Nov 27, 2017

  • OSLQuery::Parameter -- add copy/move constructors

  • Make the ShadingSystem side of OSLQuery correctly report default vals.

isstruct(false), isclosure(false), data(NULL)
{ }

Parameter () {}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any need to declare these? Don't you just want the "default" behavior?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the copy and move constructors, it's important that the data pointer refers to ITS OWN default field, not a straight pointer copy from the source. So default ctrs won't work.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok with this?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I missed that detail.

LGTM!

* OSLQuery::Parameter -- add copy/move constructors

* Make the ShadingSystem side of OSLQuery correctly report default vals.
@lgritz lgritz merged commit bd28ff1 into AcademySoftwareFoundation:master Nov 28, 2017
@lgritz lgritz deleted the lg-oslquery branch November 28, 2017 04:38
lgritz added a commit to lgritz/OpenShadingLanguage that referenced this pull request Nov 28, 2017
* OSLQuery::Parameter -- add copy/move constructors

* Make the ShadingSystem side of OSLQuery correctly report default vals.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants