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

Be more professional in API naming. #9

Open
rainwoodman opened this issue Aug 8, 2016 · 1 comment
Open

Be more professional in API naming. #9

rainwoodman opened this issue Aug 8, 2016 · 1 comment

Comments

@rainwoodman
Copy link
Collaborator

Shall we do the following renaming in the API:

BigFile -> Group
BigBlock -> Column
BigData -> DataSet
@rainwoodman
Copy link
Collaborator Author

Python API is updated.

The C-API will probably stay the way it is, because it is not worth it to add a lot of new code to provide the backward compatibility.

Unless we do this in two phases -- first add an-alias to bigfile/legacy that has the old code, then do the breakage and add the new code; and when downstream breaks, they can use the relatively stable legacy API till they decide to migrate with 'search/replace'.

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

1 participant