Programming Forums - View Single Post - Passing encrypted string through socket, weird behavior?

DaWei · Dec 29th, 2006, 5:50 PM

I doubt that your problem is with C++, per se. Octal 012 is a newline. I'm not surprised
to find one at the end. I suggest that your problem is in the handling. You don't say
much about that (system, OS, mechanism being used to make the transfer, or write the
file). You would have more luck interpreting the contents of your string if you looked at
it in hexadecimal format. Those '.'s could be anything. If there's a Windows stream
involved, and it's in default text mode, 0x1a will behave as an end-of-file indicator.

Nice job blowing the width to hell just to preserve '.'s that aren't readable, anyway

.

Dec 29th, 2006, 5:50 PM	#3
DaWei Resident Grouch Join Date: Jun 2005 Posts: 6,453 Rep Power: 10	I doubt that your problem is with C++, per se. Octal 012 is a newline. I'm not surprised to find one at the end. I suggest that your problem is in the handling. You don't say much about that (system, OS, mechanism being used to make the transfer, or write the file). You would have more luck interpreting the contents of your string if you looked at it in hexadecimal format. Those '.'s could be anything. If there's a Windows stream involved, and it's in default text mode, 0x1a will behave as an end-of-file indicator. Nice job blowing the width to hell just to preserve '.'s that aren't readable, anyway . __________________ Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers