Message from discussion
NAMELIST questions raised while testing it's use in parsing ?command line arguments
Path: g2news2.google.com!news3.google.com!feeder.news-service.com!news-out1.kabelfoon.nl!newsfeed.kabelfoon.nl!xindi.nntp.kabelfoon.nl!teleglobe.net!teleglobe.net!news.linkpendium.com!news.linkpendium.com!pit-transit.telstra.net!news.telstra.net!news-server.bigpond.net.au!53ab2750!not-for-mail
From: "robin" <robi...@bigpond.com>
Newsgroups: comp.lang.fortran,comp.lang.pl1
References: <95828284-bfef-4c90-8633-9104f8aaa9cd@o21g2000vbl.googlegroups.com> <Cml5QFDwpomKJwZI@page.demon.co.uk> <Lfwmm.293$Jd7.9@nwrddc02.gnilink.net> <V0Tc0QBob6mKJw7t@page.demon.co.uk> <e1a57d2f-c17a-4d10-b9f4-103469fdf9a7@r34g2000vba.googlegroups.com> <h7h65m$917$1@naig.caltech.edu> <S56nm.15192$ze1.3908@news-server.bigpond.net.au> <Mydnm.43374$PH1.7282@edtnps82> <h7jq06$41s$1@naig.caltech.edu> <h7kd6d$j7s$1@news.eternal-september.org>
Subject: Re: NAMELIST questions raised while testing it's use in parsing ?command line arguments
Lines: 27
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Message-ID: <CVvnm.15472$ze1.6294@news-server.bigpond.net.au>
Date: Wed, 02 Sep 2009 15:10:26 GMT
NNTP-Posting-Host: 144.139.71.122
X-Complaints-To: abuse@bigpond.net.au
X-Trace: news-server.bigpond.net.au 1251904226 144.139.71.122 (Thu, 03 Sep 2009 01:10:26 EST)
NNTP-Posting-Date: Thu, 03 Sep 2009 01:10:26 EST
Organization: BigPond Internet Services
"Peter Flass" <Peter_Fl...@Yahoo.com> wrote in message
news:h7kd6d$j7s$1@news.eternal-september.org...
> glen herrmannsfeldt wrote:
>> Also, the PL/I EDIT directed output has some interesting difference
>> to Fortran FORMAT directed output. Among others, it stops just
>> after the last list item has been used. Like C printf, it is a
>> stream mode (non-advancing in Fortran terms), so it is easy to
>> generate complicated lines built up from many such statements.
>>
>> There isn't a form that allows interpreting a character string
>> as a format string, but otherwise the actual format description
>> is a little more powerful than in Fortran.
>
> I was sure there was at least one PL/I compiler that had a nonstandard
> builtin that would encode a character string as a format, but I can't find
> the reference just now. At any rate, the combination of remote format
> statements and expressions in the format specification allows just about
> anything.
The fact that PL/I accepts expressions for the repeat factor, the width,
and the number of decimal places, etc, meant that it is unnecessary to
generate special formats a la Fortran.
Nevertheless, the EDIT built-in function permits formats to be built up
at run time, if required.