Follow

my paper got published! (Comp Sci) 

Hi folks, my paper "Making legacy Fortran code type safe through automated program transformation" has just been published in Journal of Supercomputing, as Open Access:

"We present the first rigorous analysis of the type safety of FORTRAN 77 and the novel program transformation and type checking algorithms required to convert FORTRAN 77 subroutines and functions into pure, side-effect free subroutines and functions in Fortran 90.
We show that the resulting code is type safe and that the pure, side-effect free and referentially transparent subroutines can readily be offloaded to accelerators."

link.springer.com/article/10.1

Web 6 22 36

my paper got published! (Comp Sci) 

@wim_v12e
Congratulations!!

my paper got published! (Comp Sci) 

@Callalily Thank you!

re: my paper got published! (Comp Sci) 

@wim_v12e 銇娿倎銇с仺銇嗐仈銇栥亜銇俱仚

re: my paper got published! (Comp Sci) 

@jk 銇┿亞銈傘亗銈娿亴銇ㄣ亞锛

my paper got published! (Comp Sci) 

@wim_v12e congrats! :)

my paper got published! (Comp Sci) 

@wim_v12e WOW! Congratulations, Wim! ^_^

my paper got published! (Comp Sci) 

@Eidon Thank you very much! I'm very happy about this because I wrote this at a time when I had very little time for research, so it is good to see some result.

my paper got published! (Comp Sci) 

@wim_v12e @Eidon cheers!

my paper got published! (Comp Sci) 

@amaral @Eidon Thanks!

my paper got published! (Comp Sci) 

@wim_v12e //Wow, I'm surprised, I didn't know there were still lines of research in Fortran.

my paper got published! (Comp Sci) 

@jar We make our own 馃槂 But I was also surprised that the Fortran type system had never been formalised.

my paper got published! (Comp Sci) 

@wim_v12e //I can't fully understand what you're saying, but only fortunately I never had to program in Fortran, they say it's complex.
I don't know your area of research, but I imagine fortran 2018 already has type safety. But with regard to research, wasn't it enough to create a new library in the language and rebuild? (I'm a complete ignorant on this topic, I'd better read the post) XD

my paper got published! (Comp Sci) 

@jar Fortran is not complex, on the contrary. It's much easier than C.
Fortran 2018 is fully backwards compatible with Fortran 77 so the issues are discuss apply to it as well. You can of course write type-safe programs in any version of Fortran, including F77, as long as you don't use the unsafe features. But the language itself is not type-safe.
I don't understand how a library would solve the type safety issue, can you elaborate a bit?

my paper got published! (Comp Sci) 

@wim_v12e // i mean it might be similar to using <ctype.h> in C. But again, I'm a complete ignoramus in your area of study.

my paper got published! (Comp Sci) 

@jar Ah, I see. The reason why F77 is not type safe is not to do with the types themselves. There are certain constructs in the language that erase all type information irretrievably, similar to casting anything to (void*).
My main contribution is a check to see if these constructs are actually unsafe in a given program, and a transformation to get rid of them if they are safe. If the code is unsafe, that is a type error and it won't compile.

my paper got published! (Comp Sci) 

@wim_v12e /I see, great! I will read the paper for details. congratulations.

Sign in to participate in the conversation
Octodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!