Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is pxr::TfDiagnosticBase::GetPrettyPrintString meant to be public? #1942

Closed
lpapp opened this issue Jul 9, 2022 · 3 comments
Closed

Is pxr::TfDiagnosticBase::GetPrettyPrintString meant to be public? #1942

lpapp opened this issue Jul 9, 2022 · 3 comments

Comments

@lpapp
Copy link

lpapp commented Jul 9, 2022

Description of Issue

Currently, it is not marked with TF_API, so the linker would fail on Windows when trying to use them. GetCommentary seems to do the same inline, so maybe we are meant to use that instead? But then, why is GetPrettyPrintString part of the public API documentation?

Steps to Reproduce

  1. std::cout << tfError.GetPrettyPrintString() << std::endl;

System Information (OS, Hardware)

Windows 10

Package Versions

22.05

@lpapp lpapp changed the title Is pxr::TfDiagnosticBase meant to be public? Is pxr::TfDiagnosticBase::GetPrettyPrintString meant to be public? Jul 11, 2022
@sunyab
Copy link
Contributor

sunyab commented Jul 11, 2022

Filed as internal issue #USD-7481

@sunyab
Copy link
Contributor

sunyab commented Jul 29, 2022

Hi @lpapp, that GetPrettyPrintString function is legacy code that should be removed in favor of GetCommentary. We'll fix that, along with adding TF_API to the other public functions in that class. Thanks for calling our attention to this!

@lpapp
Copy link
Author

lpapp commented Jul 30, 2022

Yes, that is what we ended up using after I saw that issue. It is great to get feedback on this as it seems we took the same decision. So, we are on the same page, thank you so much!

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

No branches or pull requests

2 participants