# HG changeset patch
# User HackBot
# Date 1358762827 0
# Node ID 9ce3afae89b0ed5d241f5beca2b748e584b50581
# Parent  98095230612b077b46ca0cfafb1f4ee283b8eb15
<oerjan> pastelogs fueue.*eof

diff -r 98095230612b -r 9ce3afae89b0 paste/paste.424
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/paste/paste.424	Mon Jan 21 10:07:07 2013 +0000
@@ -0,0 +1,7 @@
+2012-08-29.txt:13:14:07: <oerjan> hm fueue has no EOF detection
+2012-08-29.txt:13:36:46: <fizzie> oerjan: If the "read character" Fueue 'operation' returns -1 for EOF, then the empty-program cat will in fact print an infinite amount of -1's after the actual contents.
+2012-08-29.txt:13:42:14: <fizzie> A Fueue cat that properly halts on EOF (assuming EOF = read -1) sounds like a nice little exercise for you folks, too.
+2012-08-29.txt:13:42:15: <oerjan> atriq: WHAT DO YOU WANT TO HAPPEN IN FUEUE WHEN EOF IS READ
+2012-09-27.txt:20:38:51: <Arc_Koen> atriq: I've been thinking, it seems rather logic to me that Fueue programs should end when they try to input but reach EOF
+2012-09-27.txt:21:15:51: <Arc_Koen> oerjan: do you think Fueue would be TC, using its input system as input, if EOF halted execution?
+2013-01-21.txt:10:06:39: <oerjan> `pastelogs fueue.*eof