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: [fortran,patch] Towards wide character strings, step 2: handle characeter constants as wide strings

From: FX <fxcoudert at gmail dot com>
To: Tobias Burnus <burnus at net-b dot de>
Cc: Fortran List <fortran at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 6 May 2008 21:45:48 +0100
Subject: Re: [fortran,patch] Towards wide character strings, step 2: handle characeter constants as wide strings
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; bh=WnKdQ+hPnytooDuJ8MtoPdEU+vjjq2amaLf2Pkmh0Rs=; b=WPu+xaxtbPSPIOaZkpWp7sLi6xbbif8kn8TCxWI3jwPsrX0aoCHZ6vwaFcciGhSa+ReNe4/8PUlMzuOjRhsjLAKDYOFn6x1tn3kcyK8HPBXWY59uectzeAc5F4hdsIbByhPGGH3Wp0zep8LMLVLv3DkXhBVsKz5xc1Kml8R8Qto=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=FdpexWBOiKKwoj6iBtP4ph+98KW0r3Ivh786L4gkyFwAaKcKQskn7ZT138W5mZBZfVpHeWnKOZXyJmxL8AIEidAzcCFY0xsOarp0kdcNfAgYg50LRKA18SjsICrXbAVXUWjgqeAr3WCTUP6dw4YRAhl0ETSO8/dhr4gb0n4gQtE=
References: <0BE4DDAB-18E8-46B3-BE3C-1415C83E7141@gmail.com> <4820A5F1.8070709@net-b.de>

OK to commit?
OK.

Thanks.

On has then also decide whether on allows, e.g. character(selected_char_kind('ISO_10646')) :: a = 'x' I think this is not standard conform since 'x' has the default encoding whereas a is UCS-4.

Well, how is that different from:

integer(kind=8) :: i = 42_4

which is legal? The standard explains that you can assign ISO 10646, ASCII, or default character exprs to ISO 10646, ASCII, or default character variables (7.4.1.2 in F2003).

Simply print an error for non-ascii Hollerits. Hollerit constants were deleted from F77 and Hollerit edit descriptors were deleted from Fortran 95. I think there exists no program which uses non- ascii characters for Hollerits. Before Fortran 77 I think there was no one thinking of non-ascii characters and after Fortran 77 no one should have used Hollerit constants anymore. (If creating an error is too difficult, one could also simply place a note in the Hollerit section of gfortran.tex.)

Fine for me :) I'll go for the error, it should be rather simple.

PS: The following program now causes an ICE (with -fbackslash):
module m
 character(*), parameter ::  a ='H\0z'
end module m
use m
print *, a  ! ICE
end
! ICE: in gfc_widechar_to_char, at fortran/scanner.c:202

According to the gfortran documentation one has 'H', '\0' and 'z'. There is no wide character involved.

Agreed that it's how it should behave. I'm on it!

Thanks again,
FX

--
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/

Follow-Ups:
- Re: [fortran,patch] Towards wide character strings, step 2: handle characeter constants as wide strings
  - From: Tobias Burnus

References:
- [fortran,patch] Towards wide character strings, step 2: handle characeter constants as wide strings
  - From: FX
- Re: [fortran,patch] Towards wide character strings, step 2: handle characeter constants as wide strings
  - From: Tobias Burnus

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