- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just a warning: After installation of XE Composer 2016 I found out that I am not able anymore to build projects using the Winteracter library, neither with Microsoft VS nor with the WiDE development environment provided by Winteracter. ISS, the originator of Winteracter, admitted that there are problems with XE 2016 not solved in the current editions of Winteracter. I was told that they are working on a solution, but it will take time, at least til the next update (or even longer). Sorry for the bad news. Or has a fellow developer made different experiences with XE 2016 and Winteracter?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the nature of the problem? I haven't seen previous reports of this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subroutines containing Winteracter calls did not compile although the include and library file names necessary for Winteracter are specified in the VS options. The WiDE environment of Winteracter seems to have similar problems. I am sorry that I cannot be more specific. I am not able to reproduce the error, because I deinstalled XE 2016 rightaway and reinstalled XE 2015 again to get urgent work done. Maybe a specialist from ISS could comment on the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FYI: I'm using Intel 2016 (x64) with Winteracter 10.0g and haven't had any problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I also have XE2016 and Winteracter 10.0f, and have no problems related to Winteracter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am glad to hear that other users of XE2016 and Winteracter 10 did not have any problems. I forgot to mention that I use Winteracter 9.20. Maybe the Winteracter versions behave differently, and it's time for an upgrade to Winteracter 10. Thanks for your comments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To be clear, we have most definitely not "admitted that there are problems with XE 2016 not solved in the current editions of Winteracter". That is a misquotation of the advice we actually provided.
For the benefit of other Winteracter users who may have been misled by Rase's initial statement, this is the advice we actually gave:
"The current version of Winteracter supports Intel Visual Fortran versions 10 through 15, with Visual Studio versions up to and including
VS 2013. We have not yet had the opportunity to verify compatibility with either IVF 16.0 ("XE 2016") or VS 2015. It is our intention to add formal support for these recent releases in the next version of Winteracter. We aim to release that later in the year."
As can be seen, we made no reference to there being "problems" with XE 2016. The current situation is exactly as stated above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Winteracter: Sorry for misunderstanding your message. I will attempt to get XE2016 and Winteracter 9.20 running together as soon as possible. In the past I had occasional problems when I tried to update IVF. A clear solution is to deinstall the old version before installing the update, although that procedure should not be necessary. Maybe that's the reason for the problems I had.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page