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

Zcmtype data-members can have naming collisions with generated function-members #178

Closed
olsoni opened this issue Jan 24, 2018 · 3 comments
Closed

Comments

@olsoni
Copy link
Member

olsoni commented Jan 24, 2018

This is a particularly nasty undocumented restriction of the member names of zcmtypes. In particular, the potential collisions are language specific and will raise errors at different parts in the compile process (if at all). We should at the very least make zcm-gen fail if it detects a naming collision.

@jbendes
Copy link
Member

jbendes commented May 29, 2019

This has been implemented for language keywords, but you're right that we forgot to include function names from zcm too. We should take a look at this again

@jbendes
Copy link
Member

jbendes commented Sep 28, 2021

Is there an example for this?

@jbendes
Copy link
Member

jbendes commented Oct 8, 2023

handled in #457

@jbendes jbendes closed this as completed Oct 8, 2023
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