| Server IP : 66.29.132.122 / Your IP : 3.22.249.89 Web Server : LiteSpeed System : Linux business142.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64 User : admazpex ( 531) PHP Version : 7.2.34 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /proc/self/root/proc/self/root/proc/thread-self/root/proc/thread-self/root/proc/self/root/proc/thread-self/root/proc/self/root/proc/self/root/opt/alt/ruby18/share/ri/1.8/system/IO/ |
Upload File : |
--- !ruby/object:RI::MethodDescription aliases: [] block_params: comment: - !ruby/struct:SM::Flow::P body: The trick here is doing a match where you grab one <b>line</b> of input at a time. The linebreak may or may not occur at the boundary where the string matches a format specifier. And if it does, some rule about whitespace may or may not be in effect... - !ruby/struct:SM::Flow::P body: That's why this is much more elaborate than the string version. - !ruby/struct:SM::Flow::P body: "For each line: Match succeeds (non-emptily) and the last attempted spec/string sub-match succeeded:" - !ruby/struct:SM::Flow::VERB body: " could the last spec keep matching?\n yes: save interim results and continue (next line)\n" - !ruby/struct:SM::Flow::P body: "The last attempted spec/string did not match:" - !ruby/struct:SM::Flow::P body: are we on the next-to-last spec in the string? - !ruby/struct:SM::Flow::VERB body: " yes:\n is fmt_string.string_left all spaces?\n yes: does current spec care about input space?\n yes: fatal failure\n no: save interim results and continue\n no: continue [this state could be analyzed further]\n" full_name: IO#scanf is_singleton: false name: scanf params: (str,&b) visibility: public