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

Better name for FLVariablesMapping #129

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments
Open

Better name for FLVariablesMapping #129

GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

I would reserve the Mapping word for the hierarchy of FLMapper.

Original issue reported on code.google.com by tinchod...@gmail.com on 22 Dec 2011 at 6:26

@GoogleCodeExporter
Copy link
Author

FLClassShapeEncoderDecoder
FLClassShapeWriterReader
FLClassShapeSerializer

The same as above but FLClassInformationXXX


I don't like the "variables" beacuse it is misleading. We write all the 
information in order to handle class reshape. So it is (or could be in the 
future) more than just "variable mapping"

Original comment by marianopeck on 5 Jan 2012 at 4:37

@stale
Copy link

stale bot commented May 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant