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

Suggestion to fix bugs. #2

Closed
GoogleCodeExporter opened this issue Mar 13, 2015 · 3 comments
Closed

Suggestion to fix bugs. #2

GoogleCodeExporter opened this issue Mar 13, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

there is many bugs (for example longer expressions). Fixing them has higher 
priority than new features IMHO :)

Original issue reported on code.google.com by jakub.hu...@gmail.com on 25 Aug 2010 at 1:20

@GoogleCodeExporter
Copy link
Author

Original comment by jakub.hu...@gmail.com on 25 Aug 2010 at 1:21

  • Added labels: Type-Task, Priority-High
  • Removed labels: Type-Defect, Priority-Medium

@GoogleCodeExporter
Copy link
Author

For example:

s:array(1..300)
bb =s(5 and $ff)
bb =s((5))
bb =s((5) and $ff)
"[bb]"

Original comment by jakub.hu...@gmail.com on 25 Aug 2010 at 1:42

@GoogleCodeExporter
Copy link
Author

I agree. It is good to have the features at least in rudimentary state, as they 
affect the way translate and optimize phases are done and it is better to count 
with then from the beginning (or at least as soon as possible).

I fixed the example you found and will fix all other found bugs with top 
priority.


Original comment by rudla.ku...@gmail.com on 27 Aug 2010 at 4:53

  • Changed state: Fixed

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