forums.silverfrost.com

[KL]

Approximately 4 weeks ago, Robert had sent me the alpha version of the new Visual Studio (VS) 2017 Fortran plugin for testing. This version works very well, and -for the moment- only minor issues need further attention. For my work, this is an essential contribution for using Fortran within VS and I would like to acknowledge Robert�s work.
Just a comment to the question why using VS:
For large Fortran projects I prefer VS instead of Plato. Advantages are
- VS has been designed for large projects
- Same IDE for projects in different languages
- An excellent tool for developing any GUI by offering a graphical designer window, with a comprehensive toolbox for controls etc., which can easily be configured (size, location, font, colors). The switch between design view and code view allows a seamless development.
- Projects written in different languages can be combined in one solution.
Size and complexity of VS may be considered as disadvantage. However, in contrast to several remarks in this forum, I consider the more or less �continuous� update of versions (similar to Windows 10) as uncritical.
Thus, I am awaiting the official release of the VS 2017 plugin with greatest interest.
Klaus

[LitusSaxonicum]

Klaus,
While not explicitly answering my questions, your recent post clarifies some issues for me in a helpful way. If I may paraphrase your answers:
1. You like VS better than PLATO.
2. VS is better for large projects.
3. VS integrates different languages better (and here I assume computer languages).
4. VS has a visual design mode.

[LitusSaxonicum]

... continued (for some reason the Forum posted my incomplete message and won't let me edit it).

So (1) is a matter of taste, fair enough. As far as (2) goes, what is the definition of 'big', and does PLATO actually have a size limitation? (3) Seems fair enough, but then that doesn't apply to anyone who uses just Fortran. I can see that (4) could be a real issue for some. Many thanks for the insight.

Eddie

[PaulLaidler]

Early versions of Plato had problems with dependency checking. This was particularly apparent for large projects. The current Plato works well with large projects as far as I know.

[KL]

Last summer, I had some problems with Plato to define a Fortran project consisting of approximately 550 subroutines or functions. I had to include the files in several 'packages' of about 100 routines. After I had included such a 'package' the dependency checker started to work automatically, which I did not noticed immediately. Any attempt to include further files ended in a disaster. So it took some time to build up the project.

I also had a problem with Plato's dependency checker when I modified a global variable in a module, which is used in more or less all routines.

I am glad to hear that these problems have been solved and I will have a look to Plato again when the latest ftn95 PE version will be released.

I completely agree with your comments, Eddie. Of course, we should always keep things as simple as possible.

Klaus

[KL]

Last summer, I had some problems with Plato to define a Fortran project consisting of approximately 550 subroutines or functions. I had to include the files in several 'packages' of about 100 routines. After I had included such a 'package' the dependency checker started to work automatically, which I did not noticed immediately. Any attempt to include further files ended in a disaster. So it took some time to build up the project.

I also had a problem with Plato's dependency checker when I modified a global variable in a module, which is used in more or less all routines.

I am glad to hear that these problems have been solved and I will have a look to Plato again when the latest ftn95 PE version will be released.

I completely agree with your comments, Eddie. Of course, we should always keep things as simple as possible.

Klaus