SMSLink Server - KNOWN BUGS===========================(last modified on 21/02/99)(01/09/98)* When the parser experience a "parse error" (typing mistake, command not recog-  nized by the grammar), an error message is generated all right, but the next  command(s) to be issued, correct or not, won't be processed. You first have to  press [return] a few times (as many times as there are words in the first, in-  correct command line) to "purge the buffer" that's still holding this line.* Specially for the "set" command, the input buffer size defined by default by  lex doesn't seem to be quite enough. When a very long string is keyed in, a  "parse error" will be generated, due to the fact that the closing quote won't  be seen by the parser. You then have to press [return] quite a few times to  purge the buffer (see previous bug).  Some side effect here is the fact that if the original string contained a  sequence of words meaningfull to the language, they might get executed.(02/09/98)* The interactive interface (command prompt) is not displayed correctly when  accessed from a DOS/Windows machine. To display the strings correctly, I had  to replace '\n' char. by "\r\n". This fix doesn't seem to affect the Unix  clients (using standard telnet) in the least.    But even then, a "parse error" is generated for each character that the DOS/  Windows client is sending (even though the yytext string seems to contain  only that character).    UPDATE : the telnet client have to implement "line mode", not "character  mode". I was able to configure Reflection ver. 6 (32bit) to do so (see varia  directory, a file called SMS.R1W). But neither the telnet applet that ships  with Win95 or WinNT, nor older versions of Reflection seem able to support  that. So it would be much better to handle this on the server side.