On Tue, Nov 19, 2019 at 03:53:16AM +0100, Florian Obser wrote:

> On Tue, Nov 19, 2019 at 12:15:34AM +0100, Klemens Nanni wrote:
> > On Mon, Nov 18, 2019 at 10:19:47PM +0100, Klemens Nanni wrote:
> > > With that, my initial case is no longer misleading;  alternatively, I
> > > can implement the dash semantic, but that's another diff.
> > Hm, that makes the default setup (no /etc/unwind.conf, empty
> > unwind_flags) always print a warning, which is ugly.
> 
> It's not just ugly, it's missleading. We want unwind to be the best it
> can be *without* a config file. We don't to suggest a config file. We
> want to steer people away from pushing buttons, not towards.
> 
> Btw. I'm not sure the parser can work with stdin, I think it needs to
> seek, which you can't do on stdin? But I might be mistaken on multiple
> levels.

yacc uses a one-token lookahead parser, it needs to look at the one
extra token max to decide what to do next. It keeps track of the last
token seen itself. As for the lexers we use, they use one character
lookahead, with an occasional ungetc. stdio is guaranteed to handle
that without issues for any stream source. As for parsers or lexers
needing seek, the thought alone! ;-)

        -Otto

Reply via email to