Hi! On Thu, Feb 11, 2010 at 11:49:48AM +0100, Oliver Schmidt wrote: > The obvious workaround is to have '\n's in the printf's and live with > the blank lines inserted in other environments. Nevertheless I'd like > to know if the "CBM maintainers" consider this behaviour as an issue > to be fixed. It seems to be the way how the CBMs handle CR on stdin, if stdin is the console. Historically this wasn't defined on any operating system. On Unix (where POSIX comes from), the behaviour of the terminal is configurable via the tty subsystem. Echo can be enabled/disabled using the stty helper program. So actually even in this case, a program cannot be sure if input on the console is echoed or not. > I haven't found any standards document describing the gets() echoing > at all. However the current status is suboptimal from the platform > independence perspective. Acknowledged. But I would vote not to fix it. There's still conio, where semantics are stronger. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Feb 11 19:51:00 2010
This archive was generated by hypermail 2.1.8 : 2010-02-11 19:51:04 CET