Fortran Programming Language :: Frequently answered questions


	Frequently answered questions Instead of complaining about common questions being repeated over and over again (FAQs), I've decided it's time to just post the answers. (Let's not keep the impatient users waiting.) - implicit none - uninitialized variables - array subscript out of bounds - argument mismatch - internal read and internal write - stream i/o - try g95 or gfortran or open watcom - try a different compiler - enable debugging options - use diagnostic WRITE statements - try higher logical unit numbers - compiler errors are much less common then user errors - non standard code can do whatever it wants, including starting WW3 - kind numbers are not portable - g95 -s -mrtd -shared -o foo.dll foo.f95 foo.def - requires an explicit interface - update your compiler - contatct tech support - do your own homework - character() is not a variable length string - read the error message - RTFM -- elliot "e p chandler" <e@juno.com> wrote in message news:1177597992.338947.271490@t38g2000prd.googlegroups.com... > Instead of complaining about common questions being repeated over and > over again (FAQs), I've decided it's time to just post the answers. > (Let's not keep the impatient users waiting.) > - implicit none etc. Brilliant, but you forgot: - pointers start life with an undefined association status that cannot be tested: nullify them Regards, Mike Metcalf On Apr 26, 10:33 am, e p chandler <e@juno.com> wrote: > Instead of complaining about common questions being repeated over and > over again (FAQs), I've decided it's time to just post the answers. > (Let's not keep the impatient users waiting.) > - implicit none > - uninitialized variables > - array subscript out of bounds > - argument mismatch > - internal read and internal write > - stream i/o > - try g95 or gfortran or open watcom or (free) Silverfrost (formerly Salford) FTN95 if using Windows or Lahey Source Check http://www.lahey.com/check.htm or NAGWare f95 syntax checker http://cpc.cs.qub.ac.uk/ or FTNCHEK if using Fortran 77 > - try a different compiler > - enable debugging options If programming in F77 style without MODULEs or INTERFACES, put all sources in a single file and compile with the option to warn about mismatched arguments (present in most compilers). - Hide quoted text - > - use diagnostic WRITE statements > - try higher logical unit numbers > - compiler errors are much less common then user errors > - non standard code can do whatever it wants, including starting WW3 > - kind numbers are not portable > - g95 -s -mrtd -shared -o foo.dll foo.f95 foo.def > - requires an explicit interface > - update your compiler > - contatct tech support > - do your own homework > - character() is not a variable length string > - read the error message > - RTFM > -- elliot