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

Issue with the io Lexer #9

Open
bivab opened this issue Nov 12, 2009 · 1 comment
Open

Issue with the io Lexer #9

bivab opened this issue Nov 12, 2009 · 1 comment

Comments

@bivab
Copy link

bivab commented Nov 12, 2009

I found an issue when passing the string "()", "[]" or "{}" to Compiler tokensForString. The first token returned has its line slot set to 0.
When i pass any other string, such as "Foo bar()", the first token has the line slot set to one.

The following command should return true
Compiler tokensForString("()") at(0) line == Compiler tokensForString("a") at(0) line

@dennisferron
Copy link
Contributor

A while back when I was profiling Io using valgrind + kcachegrind, that tool found a reference to uninitialized memory in Lexer.c. Maybe the line = 0 you are seeing is uninitialized memory? I didn't have time to investigate it further at the time.

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

2 participants