Tim,
On Thursday, December 11, 2003, at 10:15 PM, Tim Jenness wrote:
>> By the way, the .F approach for preprocessable Fortran won't work
>> reliably on HFS+, since file.F and file.f are the same file.... I'd
>> suggest .fpp as an alternative extension, and just risk folk confusing
>> it with Fortran++.
>>
>
> Will that be a problem? Since there will not be both a file.F and
> file.f...
But we'd have to cope with the case where the Fortran compiler couldn't
cope with a .F file (g77 can, I imagine, but can Sun/DEC/MIPS
Fortran?), so I'd have to be able to generate the .f file from the .F
file as a separate step prior to feeding it in to the Fortran compiler.
What HFS+ tells us is that, in this day and age, as a general
principle, it's asking for trouble to rely on case as a distinguishing
feature of filenames. Even if it _is_ OK in this particular situation,
relying on case will stuff you up somewhere, somehow.
See you,
Norman
--
----------------------------------------------------------------------
Norman Gray http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow [log in to unmask]
|