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

Problem with autogeneratad type when define a Number #92

Closed
gbasso opened this issue May 20, 2014 · 2 comments
Closed

Problem with autogeneratad type when define a Number #92

gbasso opened this issue May 20, 2014 · 2 comments
Assignees
@gallandarakhneorg
Labels
bug
Milestone
0.1.0

Comments

@gbasso
Copy link

gbasso commented May 20, 2014

When var myDouble = 0d is used. The java code is not generated.

When var myDouble : Double = 0d is used, it ok.
@gallandarakhneorg
Copy link
Member

After coding some unit tests, I cannot reproduce the problem.
Could you following the given steps, and give me your feedback:

  • Update your Eclipse plugins.
  • Open a command shell.
  • Launch your Eclipse.
  • Open your project, and update your source code for reproducing the problem.
  • When the problem is occurring, copy the text that is output on the command shell's console
  • Send the log by email.
  • Send by email the file path_to_eclipse_workspace/.metadata/.log

gallandarakhneorg added a commit that referenced this issue May 21, 2014
@gallandarakhneorg
Add unit tests for issue #92.
41db00e
gallandarakhneorg added a commit that referenced this issue May 29, 2014
@gallandarakhneorg
Update the grammar for referencing the JVM objects correctly.
869615a 
This commit provides the following answers to issues:
* issue #98: the generation of the delegating functions is done one the basis of the JVM objects (in place of the tokens).
* issue #17: the uses of the types are now correctly detected. The import statements are not correctly marked when they are not used. The "organize import" feature is working.
* issue #17: referencing the JVM objects in place of the tokens should permits to the auto-completion feature to detect the proposals.
* issue #92: enforce the code of the JVM inferrer for avoiding a NullPointerException.
* issue #46: write plenty of checking functions in the validator. This avoid the Java compiler to show errors in place of the SARL compiler.
* issue #93: the current grammar, the inferrer, and the validator are now compatible with Xtext 2.6.
@gallandarakhneorg
Copy link
Member

Are the last patches fixing the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gallandarakhneorg gallandarakhneorg

Labels
bug
Projects
None yet
Milestone
0.1.0
Development

No branches or pull requests
2 participants
@gbasso @gallandarakhneorg