Furhter investigation of this issue, made me conclude that the bug was in my input. Not my code.
So, once again: Code:
bash$ cat garbled.txt |
@ HKo -- very nice :)
Compact and efficient, with as you mention, the benefit of easily translating the next chunk of such nonsense without editing the source. :cool:! Sasha |
Interesting thread...
|
Quote:
|
Quote:
The original cipher is included within the executable, so that if nothing is presented to stdin, and no file is given to it, it spews out the built-in cipher :D |
Interesting thread indeed. I laughed hard when someone actually made a lolcode solution. That was awesome! :)
|
Ditto. The lolcode was hilarious. As I said on the thread that linked me to this one, I can't thank everybody individually, but I rated the thread 5 stars - first time I felt compelled to rate a thread. Great stuff.
|
he didn't even notice after seeing the cleartext that every other letter was unencrypted....... definitely flunked for that job.....
seems to me i remember there was an early "desktop" computer that stored text data in a similar format..... can't remember if it was some kind of checksum thing or some proprietary file type so that files created with that format couldn't be read by other programs......long time ago..... maybe it was wordstar for CP/M? |
All times are GMT -5. The time now is 04:11 PM. |