Silverfrost Forums

Welcome to our forums

VS2017 updated plugin

15 Aug 2018 10:30 (Edited: 16 Aug 2018 9:52) #22472

Quoted from John-Silver ... meanwhile, Alex and Klaus (top 2 comments of this thread) are still probably awaiting a simple reply to their original enquiry which seems to have got lost the last 3 months or so (amongst the lively debate about .NET and it's usefulness or otherwise)

Wasn't it clear why no respond, John? If my vague wordswordswords and plots were not clear let's try to express the same but different way -- using language of numbers. There are around 1/1000 of all programmers who use Fortran. Out of those small fraction there are 1/1000 who are interested in NET = total 1 per million

And out of those left the 1/1000 are interested in using O-hu-plot graphics. Total = one per billion.

Meantime almost 1 out of 1 people who use programming are interested in the embedded in each and every programming language high quality, easy and intuitive graphics. Matlab demonstrated how Fortran77-like language (!!!) can overcome all other languages combined with the number of purchases among scientific and engineering masses just by integrating professional graphics callable in one click

Silverfrost would be crazy to serve 1 per billion versus - if not everyone then - at least 1 per 1000 (unless it costs them nothing in efforts and time)

15 Aug 2018 11:01 #22473

My take on anything is that if a product is advertised as doing X or supporting Y, it should work and should be kept up to date. Hence my opinion is that when SF have the opportunity, they should interface to the latest Visual Studio. I speak as one who has no interest in Visul Studio, .NET, nor things of that ilk. However, it is observable that SF have a lot of things on their plate at the moment, for example, a rash of bug fixes for 64-bit FTN95, a smaller rash of bugs in obscure areas of 32-bit FTN95, enhancements to Clearwin+ ... especially 'native' %pl. Hence one can only expect VS 2017 compatibility in the fullness of time. VS is itself a moving target, which makes things more complicated.

VS itself was going to allow us to have code that worked on all operating systems. It never delivered. Not only that, but the different versions don't seem to offer backwards or forwards compatibility, and are even picky about which version of Windows they run on.

Eddie

26 Nov 2018 5:03 #22859

I am usually the site admin.

Please login to reply.