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

Error when calling the function every. #98

Closed
gallandarakhneorg opened this issue May 27, 2014 · 1 comment
Closed

Error when calling the function every. #98

gallandarakhneorg opened this issue May 27, 2014 · 1 comment
Assignees
@gallandarakhneorg
Labels
bug
Milestone
0.1.0

Comments

@gallandarakhneorg
Copy link
Member

@gbasso and students are reporting an compilation error in Eclipse:

The method every(int, (Object)=>void) is undefined

It is due to the generation of the capacity's delegating functions.
Indeed, the following code is compiling:

getSkill(Schedules).every(x) [ doSomething ]
@gallandarakhneorg gallandarakhneorg self-assigned this May 27, 2014
gallandarakhneorg added a commit that referenced this issue May 27, 2014
@gallandarakhneorg
Rewrite the generator of the delegators to the capacity functions (is…
6a9d578 
…sue #98).

The code is enforce by parsing the Jvm model instead of the Sarl model.
@gallandarakhneorg
Copy link
Member Author

The problem seems to be fixed in the Eclipse IDE.
But it still have compilation errors on the CLI.
It may be caused by the new version of the Maven plugin coming since the upgrade to Xtend 2.6 (issue #93).

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.
This was referenced Aug 30, 2016
Closed
Closed
Closed
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
1 participant
@gallandarakhneorg