<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Oct 16, 2008 at 5:32 PM, Richard O'Keefe <span dir="ltr"><<a href="mailto:ok@cs.otago.ac.nz">ok@cs.otago.ac.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d"><br>
On 16 Oct 2008, at 8:16 pm, Paolo Bonzini wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(1) #contents is defined for file streams.<br>
There is no permission granted for implementations to give<br>
up and say "this is too hard" ("Errors" is "None" in section<br>
<a href="http://5.10.1.1" target="_blank">5.10.1.1</a>).<br>
<br>
-- How do you handle #contents for /dev/tty? Read and preserve<br>
every character until the machine is powered off, then send<br>
the results back in a time machine?<br>
</blockquote>
<br>
Simple: PEBKAC.<br>
</blockquote>
<br></div>
What the dickens does PEBKAC mean?</blockquote><div><br></div><div>Google and Wikipedia are your friends...</div><div><a href="http://en.wikipedia.org/wiki/PEBKAC">PEBKAC - Wikipedia, the free encyclopedia</a></div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
_______________________________________________<br>
ANSI-Smalltalk mailing list<br>
<a href="mailto:ANSI-Smalltalk@lists.openskills.org" target="_blank">ANSI-Smalltalk@lists.openskills.org</a><br>
<a href="http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk" target="_blank">http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk</a><br>
</div></div></blockquote></div><br></div>