Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Thomas Koenig Newsgroups: comp.compilers Subject: Re: Parsing multiple inputs, was Why no shift-shift conflicts? Date: Fri, 28 Jan 2022 19:19:49 -0000 (UTC) Organization: news.netcologne.de Lines: 15 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <22-01-118@comp.compilers> References: <22-01-112@comp.compilers> <22-01-115@comp.compilers> <22-01-116@comp.compilers> Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="73900"; mail-complaints-to="abuse@iecc.com" Keywords: parse Posted-Date: 28 Jan 2022 15:22:06 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:2875 Andy Walker schrieb: > On 28/01/2022 01:20, Kaz Kylheku wrote: > [...] >> Since there is only one input stream, there cannot be a shift-shift >> conflict. > > I suppose there is no conceivable use for a parsing process > that operates on several collateral input streams? The information about which stream the input comes from has to be around. Why not simply put an identifier for the input stream before the data, and build a conventional parser? Even a state machine with several inputs can be viewed as processing several input streams.