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

Overwrite behavior #8

Open
qlixed opened this issue Mar 27, 2017 · 1 comment
Open

Overwrite behavior #8

qlixed opened this issue Mar 27, 2017 · 1 comment

Comments

@qlixed
Copy link
Owner

qlixed commented Mar 27, 2017

Currently I simply overwrite the buffer and nothing else. This is done in this way to avoid memory leaks and other kind of issues that might appear if i change the object buffer size, this leads us to get the '\0x0\0x0...' string.
With this in mind, here is some ideas about the current situation:

  • Make a overwrite-and-get-new-string: So we get a correct "empty" string: "". This might add an extra decrement of the reference of the object.
  • Let the '\0x0...' format as a kind-of-debug option, to double check the data
@qlixed qlixed modified the milestones: 1.0, 2.0 Mar 27, 2017
@qlixed
Copy link
Owner Author

qlixed commented Apr 2, 2017

This will take some extra time and revision of the Python-C api, push to the 2.0 version milestone

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