Re: assertion 0 failed, 0.14.0

["Jason M. Felice" <jasonf@xxxxxxxxxxxxxxxx>]

Fixed.  Apparently the AS/400 is sending 0x0D (which, in ASCII is a CR) to the
terminal as though it were a valid data character.  It currently has no
special meaning, but according to this:

http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/CO2E2001/15.6.2

It's not a valid data character either.  It is now being treated as a valid
data character, although we don't know how to display it.

The fact that this is a CR in ASCII and that it seems to appear at the end of
every line in the file makes me suspicious that some sort of conversion didn't
take place properly.  This of course doesn't excuse the AS/400 for sending it
to the terminal as though it were valid data.

If you find more characters like this, let me know.

Updates to 0.14 and 0.15 in CVS will be available soon, but I'm going to 
try to knock a few more bugs out :)

-Jay 'Eraserhead' Felice
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---