Re: Re[2]: WinHugs bug: putChar (chr 255)

Hi,

> we all guess that it the source of problem :)  btw, how about reading
> chr(0) and chr(255)? i don't checked this...

Good point. Just for reference, reading from a file worked fine with
both those values. Reading from the "stdin" with 0 is impossible
because of the design of WinHugs (there is no way for a user to type a
null). Reading 255 didn't work, this has now been fixed.

Thanks

Neil