El 19/11/13 23:43, glen herrmannsfeldt escribió:
And, importantly, the code runs fairly slow. Some years ago, I was
working with simple PERL programs that could process data at 1 megabyte
per minute. Rewriting in C, I got one megabyte per second. It is not too
unusual to run 10 times slower, but
On Wed, Nov 20, 2013 at 9:43 AM, glen herrmannsfeldt
wrote:
> I also used to use a BASIC system that allowed you to stop a program
> (or the program stopped itself), change statements (fix bugs) and
> continue on from where it stopped. Not all can do that, but pretty
> much compilers never do.
Di
In comp.lang.fortran Rainer Weikusat wrote:
> glen herrmannsfeldt writes:
>> In comp.lang.fortran E.D.G. wrote:
> "E.D.G." wrote in message
> news:ro-dnch2dptbrhnpnz2dnuvz_rsdn...@earthlink.com...
>>> Posted by E.D.G. on November 19, 2013
>>> 1. PERL PDL CALCULATION SPEED VERSUS PY
glen herrmannsfeldt writes:
> In comp.lang.fortran E.D.G. wrote:
"E.D.G." wrote in message
news:ro-dnch2dptbrhnpnz2dnuvz_rsdn...@earthlink.com...
>> Posted by E.D.G. on November 19, 2013
>
>> 1. PERL PDL CALCULATION SPEED VERSUS PYTHON AND FORTRAN
>
> (snip)
>
>> This progr
2013/11/19 glen herrmannsfeldt :
> More recently, there are JIT systems which generate the intermediate
> code, but then at the appropriate time (Just In Time) compile that to
> machine code and execute it. This is common for Java, and more recently
> for languages like Matlab.
Is there a particul
In comp.lang.fortran E.D.G. wrote:
>>> "E.D.G." wrote in message
>>> news:ro-dnch2dptbrhnpnz2dnuvz_rsdn...@earthlink.com...
> Posted by E.D.G. on November 19, 2013
> 1. PERL PDL CALCULATION SPEED VERSUS PYTHON AND FORTRAN
(snip)
> This program translation project has become one of th
