Re: Parsing multiple inputs, was Why no shift-shift conflicts?

From	Thomas Koenig <tkoenig@netcologne.de>
Newsgroups	comp.compilers
Subject	Re: Parsing multiple inputs, was Why no shift-shift conflicts?
Date	2022-01-28 19:19 +0000
Organization	news.netcologne.de
Message-ID	<22-01-118@comp.compilers> (permalink)
References	<22-01-112@comp.compilers> <22-01-115@comp.compilers> <22-01-116@comp.compilers>

Show all headers | View raw

Andy Walker <anw@cuboid.co.uk> 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.

Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Why no shift-shift conflicts? Roger L Costello <costello@mitre.org> - 2022-01-25 21:58 +0000
  Re: Why no shift-shift conflicts? Kaz Kylheku <480-992-1380@kylheku.com> - 2022-01-28 01:20 +0000
    Re: Why no shift-shift conflicts? Andy Walker <anw@cuboid.co.uk> - 2022-01-28 10:13 +0000
      Re: Parsing multiple inputs, was Why no shift-shift conflicts? Thomas Koenig <tkoenig@netcologne.de> - 2022-01-28 19:19 +0000
      Re: Parsing multiple inputs, was Why no shift-shift conflicts? Andy Walker <anw@cuboid.co.uk> - 2022-01-28 19:42 +0000
  Re: Why no shift-shift conflicts? "Ev. Drikos" <drikosev@gmail.com> - 2022-01-28 15:22 +0200

csiph-web