3 ms·
I'm reminded of the fortran to c compiler f2c that was used to produce pure c implementations of lots of libraries like LAPACK. I'm curious how they will handl
by micro_cam 12y ago
I'm reminded of the fortran to c compiler f2c that was used to produce pure c implementations of lots of libraries like LAPACK.
I'm curious how they will handle things like pointer arithmetic and memory safety in C vs Go. If they mange to do so in a performant way I could see translating lots of numerical or computationally intensive code to Go so that it could be run in a shared cloud environment without worries about memory safety and without having to resort to vms for separation.
- mjcohen 12y agoIf you took arbitrary fortran, especially with i/o, the results were an unreadable mess - but they compiled and ran. For a project I had (in the early 90s iirc), I had to extensively modify the fortran and make multiple versions before the generated C was readable. Still, much easier than a rewrite.