1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 09/15/14 15:02, Volker Armin Hemmann wrote: |
5 |
> what is wrong with fortran? |
6 |
|
7 |
I don't know. Perhaps you can tell us. |
8 |
|
9 |
OT(childhood psychological trauma){ |
10 |
I find it unreadable and had unpleasant experience |
11 |
with fortran code. I actually had to **pick a compiler** |
12 |
to the existing code in order to compile and get expected |
13 |
results. After a few painful loops of "get a new compiler" - |
14 |
"compile" - "fail" I was told that ifort should handle the |
15 |
situation. I downloaded ifort (will RMS ever forgive me?) |
16 |
and found out that my processor didn't support all the |
17 |
instructions required for running ifort (SSE2). Of course |
18 |
it (code failing to compile) is programmer's fault. |
19 |
It was a part of my job so I couldn't just lay it off and |
20 |
forget about it. |
21 |
}; |
22 |
|
23 |
>> Unfortunately. First of all technically they are programers. It |
24 |
>> looks like this kind of programmers have a hard time learning |
25 |
>> another programming language. Second, major generation/simulation |
26 |
>> packages are moving on to c++. |
27 |
> |
28 |
> and that is better why? |
29 |
|
30 |
What is better? |
31 |
Suddenly, modelling in physics isn't computational mathematics |
32 |
and it's easier to think in object rather than procedures. |
33 |
|
34 |
|
35 |
-----BEGIN PGP SIGNATURE----- |
36 |
Version: GnuPG v2.0.22 (GNU/Linux) |
37 |
|
38 |
iQEcBAEBCAAGBQJUFublAAoJEK64IL1uI2ha5KEH/iBEdbQqrc0UDQFcJnZXYTVB |
39 |
evtVw0skLbCrH8ir9IgDjMwofGHQ1ReQhDQdmEf/KyIg0kdEGE4dm19SN9ihwEgn |
40 |
8JUr1Q1eHZAjhTBF0UE3GtKTgr9jrQ1PaqH9evjGQ5i5TCLZdR4BCoPbvv2e1rr7 |
41 |
90EgMPU5dPYd3aJqpOa+Ns0f7pc07RaDl2iWg9BAfJquxnTJFppcKqBi/dUfynB5 |
42 |
MKgjGuHmV4F62QOhUNS1dAmhVNm+PPUE31wSWMyegbdq3Yi5o5+jVzbDBKPwn/+4 |
43 |
jvXBcIPr+IMtl3vMAvQmA5DMM6Th1GhSblJrLSLHxFDvDNqctfrwbzAWa+j4OHo= |
44 |
=3Qk0 |
45 |
-----END PGP SIGNATURE----- |