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

Parse Warnings Not Reported at Prompt #231

Closed
brodieG opened this issue Jul 23, 2017 · 0 comments
Closed

Parse Warnings Not Reported at Prompt #231

brodieG opened this issue Jul 23, 2017 · 0 comments
Labels
Milestone

Comments

@brodieG
Copy link
Owner

@brodieG brodieG commented Jul 23, 2017

unitizer> -2147483648L
[1] -2147483648
unitizer> str(-2147483648)
 num -2.15e+09
unitizer> str(-2147483648L)
 num -2.15e+09
unitizer> str(-2147483678)
 num -2.15e+09
unitizer> str(-21474836487L)
 num -2.15e+10
unitizer> str(-2147483648L)
 num -2.15e+09
unitizer> str(-2147483647L)
 int -2147483647
unitizer> Q

| No changes recorded.
| unitizer unchanged.

Warning messages:
1: In parse(text = res) :
  non-integer value 2147483648L qualified with L; using numeric value
@brodieG brodieG added the bug label Jul 23, 2017
@brodieG brodieG added this to the 1.4.4 milestone Jul 23, 2017
@brodieG brodieG modified the milestones: 1.4.5, 1.4.4 Sep 2, 2017
brodieG added a commit that referenced this issue Nov 21, 2017
@brodieG brodieG closed this in 765ada1 Jan 6, 2018
brodieG added a commit that referenced this issue Jan 6, 2018
Fix #220, Fix #225, Fix #237, Fix #239, Fix #242, Fix #241
Fix #231, Fix #234, Fix #220, 'diffobj' wrapped in try
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.