<div dir="ltr">On Sun, Feb 26, 2012 at 16:58, Brandon Allbery <span dir="ltr"><<a href="mailto:allbery.b@gmail.com">allbery.b@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div class="im">On Sun, Feb 26, 2012 at 13:05, Alexander Batischev <span dir="ltr"><<a href="mailto:eual.jp@gmail.com" target="_blank">eual.jp@gmail.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>getWord). That's how scanf() in C and 'cin >>' in C++ behave, and I'm<br></div></blockquote></div></div></div></blockquote><div>(polemic deleted)<br><br>Uh, belated disclaimer: I've been saying for years that scanf() and fscanf() should be banished from libc, or at minimum covered with severe "don't use this. really, DON'T USE THIS." warnings as with gets().<br>
</div></div><br>-- <br>brandon s allbery <a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a><br>wandering unix systems administrator (available) (412) 475-9364 vm/sms<br>
<br>
</div>