in reply to PDL compilation problem

Did you check to see if:

One of the worst problems I find with Windows is that using any kind of command line app quickly gets to be a major pain in the a**neck.

emc

Replies are listed 'Best First'.
Re^2: PDL compilation problem
by Anonymous Monk on Nov 25, 2005 at 18:14 UTC
    F77??? My keyboard only goes up to F12!!!
[reply]
      lol... F77 = Fortran 77

      Jason L. Froebe

      Team Sybase member

      No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

[reply]
Re^2: PDL compilation problem
by BrowserUk (Patriarch) on Nov 25, 2005 at 18:12 UTC
    I find with Windows is that using any kind of command line app quickly gets to be a major pain

    If the command name is mis-spelt, or not in the path under unix, it would also have problems locating it. Why is this any worse under Windows?

    Come to that, if the command name is F77.exe, but the user/batch file invokes it as 'f77', Windows will still run it, if it is locatable, so if anything, it is slightly easier.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
Re^2: PDL compilation problem
by jschollen (Beadle) on Nov 28, 2005 at 09:05 UTC
    Absoft's command line interface is indeed called "f77".
    I also set my path correct.
    But fellow monk Madcap Laughs gave the solution to this problem on the site he mentioned.
    Thanks thou.
[reply]

In Section Seekers of Perl Wisdom