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.

Sign up for GitHub

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

Jump to bottom

Type names and namespace #29

Open
pdigiglio opened this issue Sep 1, 2016 · 1 comment
Open

Type names and namespace #29

pdigiglio opened this issue Sep 1, 2016 · 1 comment
Labels
design enhancement

Comments

@pdigiglio
Copy link
Collaborator

I think that:

  • We should use more descriptive names for our types, e.g. ACC_ID should be called AccessId; FIL_PT should be FilePath and so on;
  • Each one of our types should have its own header.

Moreover, we should scope all we do in a namespace. Any suggestion for the namespace name? Does it make sense to call it parceive, @wilhelma?
@wilhelma
Copy link
Owner

Actually, the tool is not parceive. It's the parceive trace interpreter.
So I would suggest interpreter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wilhelma @pdigiglio