Glenn, What you describe is the implied delimited string.
I am introducing the keyword STRING to indicate that the following is to be taken as a delimited string, no matter what, just like other stages that support STRING. pipe literal | spec string 1-1 1 | cons - Ready; T=0.01/0.01 11:17:37 Yes, |specs #1:=1 print #1| is what I have in mind. If you're telling me it is a bad idea, I shall desist. j. 2009/1/7 Glenn Knickerbocker <[email protected]>: > "John P. Hartmann" wrote: >> STRING is an option on SPECs to suppress looking for anything else, >> including keywords. > > OK, now I'm confused. What does "introduced" mean here? Looks to me > like you quietly introduced this keyword ages ago: > > pickpipe module pipe1a26(push > CMS/TSO Pipelines, 5741-A05/5655-A17 1.0110 (Version.Release/Mod) - > Generated 15 May 2003 at 08:58:21 > Source: z/VM > 4.4.0 Ready; > > pipe literal|specs atring 1a 1|cons > tring 1 > Ready; > > pipe literal|specs string 1s 1|cons| > s > Ready; > >> The scanning of <inputRange> is unchanged. > > I'm worried about implicit SET and <delimitedString>. How would you > interpret, say, |specs #1:=1 print #1|? Is it still a valid spec with a > delimited string, or now an invalid spec with an implicit SET and a > missing output spec? I'm worried there might be more complicated cases > where both interpretations are valid. > > ¬R >
