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

Resolve public/private ambiguities in method names #6

Open
remogatto opened this issue Aug 14, 2010 · 0 comments
Open

Resolve public/private ambiguities in method names #6

remogatto opened this issue Aug 14, 2010 · 0 comments
Labels
refactoring

Comments

@remogatto
Copy link
Owner

We should decide which of the public methods in the current API should really be public. Here below a list of candidate methods to be eventually privatized. Please, add others if it is the case.

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

No branches or pull requests
1 participant
@remogatto