This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Some experiences with "CASE"

From: Philippe Schaffnit <philippe at access dot rwth-aachen dot de>
To: Brooks Moses <bmoses at stanford dot edu>, Richard E Maine <Richard dot Maine at nasa dot gov>
Cc: fortran at gcc dot gnu dot org
Date: Sun, 21 May 2006 19:58:56 +0200 (CEST)
Subject: Re: Some experiences with "CASE"
References: <446DDA18.E2C98858@access.rwth-aachen.de> <AEFB661C-D2D3-45E3-9936-5F94ECE36C70@nasa.gov> <446DFB2A.7000209@stanford.edu>

Thanks a lot for your comments!

Regarding my first point: if you believe that a case can be made for the thinsg as they are, I see also advantages, though I would have rather expected a warning...

I'm sorry I made such a misleading example for my second point... (see second try). I take it that there is no special provision for extented ASCII characters in the standard, i.e.: this is a bug, right?

Thanks!

Philippe

PS: a better example (I hope!)
!
      PROGRAM Test
!
      CHARACTER ( LEN = 1 ) :: Letter
!
      Letter = "c"
      SELECT CASE ( Letter )
      CASE ( "c", "ç" )
        WRITE ( 6, "(A)" ) "Expected"
      CASE DEFAULT
        WRITE ( 6, "(A)" ) "Surprising"
      END SELECT
!
      END PROGRAM Test
!
PPS: so this lands in the default!

Follow-Ups:
- Re: Some experiences with "CASE"
  - From: Brooks Moses

References:
- Some experiences with "CASE"
  - From: Philippe Schaffnit
- Re: Some experiences with "CASE"
  - From: Richard E Maine
- Re: Some experiences with "CASE"
  - From: Brooks Moses

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]