Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpda!hpcupt1!hpcllla!hpclisp!hpclcdb!cdb From: cdb@hpclcdb.UUCP Newsgroups: comp.lang.fortran Subject: Re: HP Fortran problems Message-ID: <6690006@hpclcdb.HP.COM> Date: Thu, 3-Dec-87 16:58:29 EST Article-I.D.: hpclcdb.6690006 Posted: Thu Dec 3 16:58:29 1987 Date-Received: Tue, 8-Dec-87 06:40:52 EST References: <429@auvax.UUCP> Organization: HP ITG/ISO Computer Language Lab Lines: 19 Unfortunately, the Fortran 66 standard was too weak to really standardize very much. Fortran 77 added the CHARACTER data type to handle these kind of problems. Actually, the official Fortran 66 standard did not allow quoted character strings. It had Hollerith constants, but even they were only allowed "in the argument list of a CALL statement and in the data initialization statement" (ANSI X3.9-1966, p.10). At least that shows a way around your problem - you could roll it back to real F66, by converting the quoted strings to Hollerith (at least in DATA statements). The previous response (at least on my machine) suggested moving such things forward to F77, using CHARACTER variables to hold character data. Strange idea, very un-Fortranlike! :-) You might note that Hollerith constants were removed by the 77 standard, and are unlikely to reappear in the standard (though most implementations will continue to have them). In practice, I'd do whichever looked easiest. Carl Burch hplabs!hpda!cdb