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

Class Relies on other Class with Less Strict Void Safety Settings #62

Closed
ljr1981 opened this issue Jul 8, 2013 · 12 comments
Closed

Class Relies on other Class with Less Strict Void Safety Settings #62

ljr1981 opened this issue Jul 8, 2013 · 12 comments

Comments

@ljr1981
Copy link

ljr1981 commented Jul 8, 2013

The following error stops the clean compile of the "simple" project when opening for the first time in Windows.

    Description Location    Position    
2   VD88: A class relies on another class with less strict void safety settings. Provider class: WSF_DEFAULT_SERVICE.   APPLICATION (simple)    10, 2   
    Error code: VD88

Configuration error: a class relies on another class with less strict void safety settings.
What to do: change void safety options so that ancestor or supplier provides higher or equal void safety.

Class: APPLICATION
Other class: WSF_DEFAULT_SERVICE
Line: 10
inherit
-> WSF_DEFAULT_SERVICE
redefine

I have double-checked each target to ensure it is set to Complete Void Safety. Not sure what is wrong.

@ljr1981
Copy link
Author

ljr1981 commented Jul 8, 2013

I located the tutorial project ECF's and got the same issue. The problem appears to be in the:

path: "[user_path]\EWF-0.3\library\server\wsf\default\nino-safe.ecf"

In the tutorial "hello" target, the error is the same:

    Description Location    Position    
2   VD88: A class relies on another class with less strict void safety settings. Provider class: WSF_DEFAULT_RESPONSE_SERVICE.  HELLO_APPLICATION (src) 17, 2   
    Error code: VD88

Configuration error: a class relies on another class with less strict void safety settings.
What to do: change void safety options so that ancestor or supplier provides higher or equal void safety.

Class: HELLO_APPLICATION
Other class: WSF_DEFAULT_RESPONSE_SERVICE
Line: 17
inherit
-> WSF_DEFAULT_RESPONSE_SERVICE

@oligot
Copy link
Member

oligot commented Jul 9, 2013

Hi,

Which version of EiffelStudio are you using ?
Do you use the version of EWF that comes bundled with EiffelStudio or the Git one ?

@jocelyn
Copy link
Member

jocelyn commented Jul 10, 2013

Indeed one need to apply a commit I made on the master to ensure all compile fine.

I am in vacation right now until end of July.
I may try to fix it when I find a computer but if Javier or Olivier could fix it this would help me.

For now either use eiffelstudio 7.3 with the EWF lib delivered with 7.3. Or use the master branch of EWF

@oligot
Copy link
Member

oligot commented Jul 10, 2013

Just realized I'm not part of the EiffelWebFramework Owners Team so I won't be able to fix it as I don't have the right to 😞
@jvelilla : can you fix it ?

@jvelilla
Copy link
Member

Just to double check, we want to merge the release-03 branch with the master branch?

@oligot
Copy link
Member

oligot commented Jul 10, 2013

From what @jocelyn said, I think we can just cherry-pick commit 8040dd5 on the release-03 branch and release a new tag (something like v0.3.1)

@ljr1981
Copy link
Author

ljr1981 commented Jul 15, 2013

Using v. 7.2, but curious to know what changes are in 7.3 that facilitate the EWF.

@jocelyn
Copy link
Member

jocelyn commented Jul 15, 2013

Quick reply

7.3 introduces the notion of complete void safety.
And I tried to have most of the ewf libs at this level. But this was
breaking the 7.2 compilation so I reverted some changes in the master
branch to support 7.2
But I forgot to apply this change to v0.3 because for me this was mainly
for Eiffel studio 7.3 and thus this was not an issue for 7.3 itself.

Hopefully Olivier and Javier corrected this since I am currently in
vacation.

I hope this is clear now = all my mistake.

Jocelyn
Le 15 juil. 2013 02:13, "Larry Rix" notifications@github.com a écrit :

Using v. 7.2, but curious to know what changes are in 7.3 that facilitate
the EWF.


Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-20947357
.

@oligot
Copy link
Member

oligot commented Jul 15, 2013

Thanks to Jocelyn, I'm now part of the EWF Owners Team 😏
I've updated the release-0.3 branch and also created a new tag v0.3.1.

@ljr1981 : can you update your local repository and try again ?

@ljr1981
Copy link
Author

ljr1981 commented Jul 17, 2013

I will try today! :-) Thank you folks!

@jocelyn
Copy link
Member

jocelyn commented Jul 30, 2013

Larry, can you confirm this issue is fixed?
If not, please let use know

@ljr1981
Copy link
Author

ljr1981 commented Aug 25, 2013

I am not entirely certain, but the issue seems to have been a confusion based on the different void-safety settings in 7.3 v. 7.2 and I was opening the project in 7.2. I had a similar issue with another project and then noted the differences in the void-safety settings. Having downloaded 7.3 GPL for my local laptop, there appears to be no issue. I think you can close this one out.

@ljr1981 ljr1981 closed this as completed Aug 25, 2013
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

4 participants