|
|
 Up |
|
|
  |
Author: James Van BuskirkJames Van Buskirk Date: Nov 22, 2007 12:17
While the issue has been raised about diagnostics and features that
cost the programmer time, I thought I would point out a few that I
have been bitten by lately with gfortran.
C:\gfortran\clf\bugs>C:\gfortran\win64\bin\x86_64-pc-mingw32-gfortran -v
Using built-in specs.
Target: x86_64-pc-mingw32
Configured with:
../trunk/configure --prefix=/home/FX/win64 --with-sysroot=/home
/FX/win64 --build=i386-pc-mingw32 --target=x86_64-pc-mingw32 --enable-languages=
c,fortran --with-gmp=/home/FX/local --disable-werror --disable-nls --enable-thre
ads=win32
Thread model: win32
gcc version 4.3.0 20070920 (experimental) [trunk revision 128387] (GCC)
C:\gfortran\clf\bugs>type bug1_backslash.f90
! File: bug1_backslash.f90
! Public domain 2007 James Van Buskirk
program bug1_backslash
implicit none
|
| Show full article (3.91Kb) |
|
| | 69 Comments |
|
|
Author: Tobias BurnusTobias Burnus Date: Nov 22, 2007 13:34
On Nov 22, 9:17 pm, "James Van Buskirk" comcast.net> wrote:> C:\gfortran\clf\bugs>type bug4_structure.f90
> ! File: bug4_structure.f90
> ! Public domain 2007 James Van Buskirk
> module bug4_mod
> implicit none
> type bug4
> ! Intentionally left blank; should error up here
> end type bug4
> end module bug4_mod
If you want to have an error message at that place, use -std=f95.
Fortran 2003 allows types without components.
> C:\gfortran\clf\bugs>C:\gfortran\win64\bin\x86_64-pc-mingw32-gfortran
> bug4_struc
> ture.f90 -obug4_structure
> bug4_structure.f90:13.13:
> type(bug4) t
> 1
> Error: Derived type 'bug4' at (1) is being used before it is defined
|
| Show full article (0.94Kb) |
|
| | no comments |
|
|
Author: Tobias BurnusTobias Burnus Date: Nov 22, 2007 14:08
On Nov 22, 9:17 pm, "James Van Buskirk" comcast.net> wrote:> write(*,'(a)') 'C:\windows\bug1'
>
> C:\windowug1
>
> [...] -fno-backslash [...]
> C:\windows\bug1
I don't know how to handle this best. Backslashes are difficult as
some people expect that "\" prints a backslash, others want to have
"\n" as new line -- and both want to have their choice as default.
With either choice, you have unhappy users. But I am open to
suggestions.
In the case above, the "\b" is transformed into but as \w does
not exist, it is not transformed as kept as "\" The current
implementation allows for:
character :: backslash = '\'
print *, 'Hello\nyou'
|
| Show full article (1.47Kb) |
| 1 Comment |
|
|
Author: nospamnospam Date: Nov 22, 2007 14:58
Tobias Burnus wrote:
> I don't know how to handle this best. Backslashes are difficult as
> some people expect that "\" prints a backslash, others want to have
> "\n" as new line -- and both want to have their choice as default.
> With either choice, you have unhappy users. But I am open to
> suggestions.
Well, in f0003, backslash is part of the standard Fortran character set.
So I'll find it awfully hard to accept as reasonable a default that
doesn't conform to the standard. But then I'm one of those who has
always thought that doing backslash processing on Fortan code was an
unreasonable default, so just consider me biased.
--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
|
| |
| no comments |
|
|
Author: Craig DedoCraig Dedo Date: Nov 23, 2007 06:30
"Richard Maine" wrote in message
news:1i7zirl.hdl6kepl696lN%%nospam@see.signature...
> Tobias Burnus wrote:
>
>> I don't know how to handle this best. Backslashes are difficult as
>> some people expect that "\" prints a backslash, others want to have
>> "\n" as new line -- and both want to have their choice as default.
>> With either choice, you have unhappy users. But I am open to
>> suggestions.
>
> Well, in f0003, backslash is part of the standard Fortran character set.
> So I'll find it awfully hard to accept as reasonable a default that
> doesn't conform to the standard. But then I'm one of those who has
> always thought that doing backslash processing on Fortan code was an
> unreasonable default, so just consider me biased.
>
> --
> Richard Maine | Good judgement comes from experience;
> email: last name at domain . net | experience comes from bad judgement.
> domain: summertriangle | -- Mark Twain ...
|
| Show full article (2.52Kb) |
| no comments |
|
|
Author: Dan NagleDan Nagle Date: Nov 23, 2007 07:52
Hello,
Dr Ivan D. Reid wrote:
> On Fri, 23 Nov 2007 02:07:14 -0800, glen herrmannsfeldt ugcs.caltech.edu>
> wrote in comcast.com>:
> >> There are a number of uses for backslash in strings other
>> than windows file names. TeX code, regular expression escapes,
>> unix shell escapes, to name a few. I could imagine Fortran
>> programs generating TeX output or unix shell commands.
>
> ...and PostScript(TM) graphics.
But surely all of these are rather specialized uses.
The default should be that a Fortran compiler compiles Fortran.
A specialized use can be isolated in a file or a few files
and compiled separately with special flags to do special things.
--
Dan Nagle
Purple Sage Computing Solutions, Inc.
|
| |
| no comments |
|
|
Author: Steven G. KarglSteven G. Kargl Date: Nov 23, 2007 08:08
In article comcast.com>,
glen herrmannsfeldt ugcs.caltech.edu> writes:> Tobias Burnus wrote:
>
>> On Nov 22, 11:58 pm, nos...@see.signature (Richard Maine) wrote:
>
> (snip)
>
>>>Well, in f0003, backslash is part of the standard Fortran character set.
>>>So I'll find it awfully hard to accept as reasonable a default that
>>>doesn't conform to the standard. But then I'm one of those who has
>>>always thought that doing backslash processing on Fortran code was an
>>>unreasonable default, so just consider me biased.
>
> I agree. I don't mind it as an option, but it shouldn't
> be the default. (Unless it gets added to the standard.)
>
|
| Show full article (0.93Kb) |
| no comments |
|
|
Author: Craig DedoCraig Dedo Date: Nov 23, 2007 08:10
"Dan Nagle" verizon.net> wrote in message
news:DGC1j.18697$Pt.1158@trnddc02...> Hello,
>
> Dr Ivan D. Reid wrote:
>> On Fri, 23 Nov 2007 02:07:14 -0800, glen herrmannsfeldt
>> ugcs.caltech.edu>
>> wrote in comcast.com>:
>>>>> There are a number of uses for backslash in strings other
>>> than windows file names. TeX code, regular expression escapes,
>>> unix shell escapes, to name a few. I could imagine Fortran
>>> programs generating TeX output or unix shell commands.
>>
>> ...and PostScript(TM) graphics.
>
> But surely all of these are rather specialized uses.
> The default should be that a Fortran compiler compiles Fortran.
> A specialized use can be isolated in a file or a few files
> and compiled separately with special flags to do special things. ...
|
| Show full article (1.81Kb) |
| no comments |
|
|
Author: Steven G. KarglSteven G. Kargl Date: Nov 23, 2007 08:15
In article <4746e3e5$0$19583$4c368faf@ roadrunner.com>,
"Craig Dedo" wi.rr.com> writes:> "Richard Maine" wrote in message
> news:1i7zirl.hdl6kepl696lN%%nospam@see.signature...
>> Tobias Burnus wrote:
>>
>>> I don't know how to handle this best. Backslashes are difficult as
>>> some people expect that "\" prints a backslash, others want to have
>>> "\n" as new line -- and both want to have their choice as default.
>>> With either choice, you have unhappy users. But I am open to
>>> suggestions.
>>
>> Well, in f0003, backslash is part of the standard Fortran character set.
>> So I'll find it awfully hard to accept as reasonable a default that
>> doesn't conform to the standard. But then I'm one of those who has
>> always thought that doing backslash processing on Fortan code was an
>> unreasonable default, so just consider me biased.
>
> I wholeheartedly agree with Richard. Because the backslash is part of the
> standard Fortran character set, the default behavior should be the printable ...
|
| Show full article (1.59Kb) |
| no comments |
|
|
|
|
|
Author: Gordon SandeGordon Sande Date: Nov 23, 2007 08:18
On 2007-11-23 12:10:21 -0400, "Craig Dedo" wi.rr.com> said:
> "Dan Nagle" verizon.net> wrote in message
> news:DGC1j.18697$Pt.1158@trnddc02...>> Hello,
>>
>> Dr Ivan D. Reid wrote:
>>> On Fri, 23 Nov 2007 02:07:14 -0800, glen herrmannsfeldt
|
| Show full article (2.39Kb) |
| no comments |
|
|
|
|
