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

Strings should be region allocated #149

Open
eholk opened this issue Apr 27, 2015 · 1 comment
Open

Strings should be region allocated #149

eholk opened this issue Apr 27, 2015 · 1 comment

Comments

@eholk
Copy link
Owner

eholk commented Apr 27, 2015

Right now we have no way of freeing strings once they've been allocated. We don't do a lot of dynamic string creation yet, so this hasn't caused major problems yet, but it will.

Along with this, we should create a static region where compile-time constant strings go.
@eholk
Copy link
Owner Author

eholk commented Apr 27, 2015

For now we can cheat and call free() directly.

eholk added a commit that referenced this issue May 5, 2015
@eholk
Add a read-line function (Issue #97).
adfba0d 
This reads a line of text from a file as a string. The returned string includes the trailing newline character.

This leaks memory too, because strings are not region-allocated (Issue #149)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eholk