🚀 go-pugleaf

Thanks for the helpful bug report.

The problem was that several of the istream op >> functions
used the construct

while (good()) { get(ch) ... }

when instead they should have done

if (good()) { while (get(ch)) { ... } ... }

Sorry for the slip.

Streams DO use the unix convention that you don't know if you've
reached EOF until you've tried to read a char and failed, but this
behavior is localized to get(char).

These are all fixed for the next release (1.36.0), which, at long
last, should be out within a few days.

AT&T 2.0-compatible iostream classes are in the works, but won't make it
into 1.36.0. They should be ready within a month or so.

-Doug