Live data from Hacker News

Fortran.io – a Fortran Web Framework

fortran.io

171–180 of 255 posts

Re: Fortran.io – a Fortran Web Framework

#171

Here’s an IDE for FORTRAN [1] if anyone is interested to write some programs in it. > A modern Fortran development environment for Microsoft Windows, Apple macOS, and GNU/Linux systems. It was quite interesting to read the list of available features [2]. [1] https://simplyfortran.com/ [2] https://simplyfortran.com/features/

Thanks for a shout-out to Simply Fortran! I'm the primary developer behind it (had to finally create an account to reply...), and we're always trying to improve the development environment.

ODBC? :) surely someone else needs to hit a SQL db without having a script hit the DB and pipe the data to your Fortran app?

Re: Fortran.io – a Fortran Web Framework

#172

Earlier quoted context omitted.

For sure, but their avionics software is written in Ada or C++.

And that's relevant, because... ?

How is it not? Someone said something about fighter jets being written in Fortran. Someone corrected them saying they aren't, but they are modeled using Fortran. I tried to add to the conversation by saying what they were written in assuming that would also be of interest to the person who made the original comment. I'm sorry this has perturbed you.

Re: Fortran.io – a Fortran Web Framework

#173
post #71

Earlier quoted context omitted.

I held out hope that maybe there was some sort of special treatment for that parameter. But then I looked at the source and... nope, it's just slapped on the end of the command.

I couldn't remember, but checked - I am replacing ' with _ in the actual code https://github.com/mapmeld/fortran-machine/blob/master/marsu...

Generating an SQL string with any input from the user is not accepted best practice, even if that were a sufficient way to achieve it (I suspect it would disallow a parameter string to contain a legitimate, escaped ' character).

Generally, it is recommended that you create a prepared statement entirely from static SQL string(s) (no user input) and then bind parameters into it, such that there is no possibility for any user input to be parsed as SQL:

https://www.sqlite.org/c3ref/stmt.html

Re: Fortran.io – a Fortran Web Framework

#175

It's definitely not a dead language – a new Fortran front-end has recently been accepted into the LLVM project, joining Clang. So LLVM's only in-tree supported languages (excluding the various IRs) will be C, C++, Objective-C, and Fortran. It had been scheduled for merge into the LLVM monorepo 2 days ago, but has been delayed pending some additional architecture review.

Lots of number crunching code relies on Fortran libraries even today. Install numpy, it will pull in Fortran stuff.

There are some optimizations Fortran compilers can make which C compilers cannot, though we can use the "restrict" keyword to allow C to make the same assumptions Fortran makes for aliasing pointers (ie. there are none).

However, in order to support all existing C programs I believe they still can't make the same level of optimization as Fortran does. It'd be nice to see this gap merged, in fact.

C++ can actually do better with some numeric code since commonly used libraries perform expression optimization at compile-time using Eigen for example.

Re: Fortran.io – a Fortran Web Framework

#176

It's definitely not a dead language – a new Fortran front-end has recently been accepted into the LLVM project, joining Clang. So LLVM's only in-tree supported languages (excluding the various IRs) will be C, C++, Objective-C, and Fortran. It had been scheduled for merge into the LLVM monorepo 2 days ago, but has been delayed pending some additional architecture review.

Latin was dead long before it stopped being used in written works. It died when it stopped being spoken and stopped changing. I don't know if Fortran would be considered dead by the "no longer adapting" definition, but that it's still in use isn't proof it's alive.

I work in computational fluid dynamics. Fortran is very much alive and being updated. The bigger issue, as I see it, is the adoption of newer features by current programmers. I know many people who program in modern Fortran (the 2003 and later standards with object-oriented features), but I also know some people who still program in Fortran 77 (either literally or in spirit). The second group tends to work on older "legacy" projects that may be decades old at this point. The maintainers usually decided that the cost of updating to a newer standard wasn't worth it ("if it ain't broke, don't fix it").

That said, I only write in modern Fortran when I use Fortran. The newer features make it much easier to write complex data structures, in particular.

Re: Fortran.io – a Fortran Web Framework

#177

Wow. This sounds intense and interesting. However I will stick to C++ but it is great to see power languages up and ready for new generations of hardware, software and people.

Once nice thing about Fortran's evolution is that when you lag behind the bleeding edge, you make fewer mistakes. If you like C++ that's great; you might notice that everyone else doesn't agree that it's the future.

C/C++ will be most likely used for many many decades ahead.

Re: Fortran.io – a Fortran Web Framework

#179

Earlier quoted context omitted.

And that's relevant, because... ?

How is it not? Someone said something about fighter jets being written in Fortran. Someone corrected them saying they aren't, but they are modeled using Fortran. I tried to add to the conversation by saying what they were written in assuming that would also be of interest to the person who made the original comment. I'm sorry this has perturbed you.

Ah. Thanks for the explanation.

Re: Fortran.io – a Fortran Web Framework

#180
post #177

Earlier quoted context omitted.

Once nice thing about Fortran's evolution is that when you lag behind the bleeding edge, you make fewer mistakes. If you like C++ that's great; you might notice that everyone else doesn't agree that it's the future.

C/C++ will be most likely used for many many decades ahead.

Yes? So will Cobol. So will Latin! I suspect discussing design choices might be more interesting than a popularity comparison.
Post reply on HN