Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

goto LabelHELL; 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • On a very short-lived project that I was assigned to, my primary responsibility was to port a particular astrodynamics engine to Java from C. The program had previously been ported to C from Fortran, and to Fortran from some ungodly, unknown language for an old HP paper-tape computer. I was the first actual programmer to look at said program, and all the previous ports were exactly like you described: literal translations from one language to the next.

    Function parameters were a through z. All local var

    • Indeed... It's funny how we all have passed through that.And that's funny how non-programmers choose their variables' names. This algorithm was gotten from an electrical circuits book and it's Portuguese title translates to "Electrical Circuits Course". Got it? No? They are teaching future engineers to write their programs in Basic and name their variables after A1, A2, A3, ..., Z7, Z8, Z9.

      It has just made me curious about what happens after Z9... Maybe AA1? ;-)

      The entry in my diary is like yours: variables with one letter and one number, loops using 'for', several GOTO and as the last line, a 'return'.

      I'm translating the FFT algorithm to Perl and then I'll try doing the same for C... ;o) I was originally going to translate it to C, but since I like Perl more, I've done that first.
      --
      -- Godoy.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.