#$@%#$%!

Ngiler SH3LL 360
: / opt / alt / ruby18 / share / ri / 1.8 / system / IO /

Information Server
MySQL : OFF Perl : OFF CURL : ON WGET : OFF PKEXEC : OFF

Directive	Local Value
IP Address	162.0.209.101
System	Linux premium169.web-hosting.com 4.18.0-553.50.1.lve.el8.x86_64 #1 SMP Thu Apr 17 19:10:24 UTC 2025 x86_64
User	luxeelil
PHP Version	8.0.30
Software	LiteSpeed
Doc root	Writable

Edit File : pipe-c.yaml \| Size : 1.27 KB
--- !ruby/object:RI::MethodDescription aliases: [] block_params: comment: - !ruby/struct:SM::Flow::P body: "Creates a pair of pipe endpoints (connected to each other) and returns them as a two-element array of <tt>IO</tt> objects: <tt>[</tt> <em>read_file</em>, <em>write_file</em> <tt>]</tt>. Not available on all platforms." - !ruby/struct:SM::Flow::P body: In the example below, the two processes close the ends of the pipe that they are not using. This is not just a cosmetic nicety. The read end of a pipe will not generate an end of file condition if there are any writers with the pipe still open. In the case of the parent process, the <tt>rd.read</tt> will never return if it does not first issue a <tt>wr.close</tt>. - !ruby/struct:SM::Flow::VERB body: " rd, wr = IO.pipe\n\n if fork\n wr.close\n puts "Parent got: <#{rd.read}>"\n rd.close\n Process.wait\n else\n rd.close\n puts "Sending message to parent"\n wr.write "Hi Dad"\n wr.close\n end\n" - !ruby/struct:SM::Flow::P body: <em>produces:</em> - !ruby/struct:SM::Flow::VERB body: " Sending message to parent\n Parent got: <Hi Dad>\n" full_name: IO::pipe is_singleton: true name: pipe params: \| IO.pipe -> array visibility: public Back

Edit File : pipe-c.yaml | Size : 1.27 KB

--- !ruby/object:RI::MethodDescription 
aliases: []

block_params: 
comment: 
- !ruby/struct:SM::Flow::P 
 body: "Creates a pair of pipe endpoints (connected to each other) and returns them as a two-element array of <tt>IO</tt> objects: <tt>[</tt> read_file, write_file <tt>]</tt>. Not available on all platforms."
- !ruby/struct:SM::Flow::P 
 body: In the example below, the two processes close the ends of the pipe that they are not using. This is not just a cosmetic nicety. The read end of a pipe will not generate an end of file condition if there are any writers with the pipe still open. In the case of the parent process, the <tt>rd.read</tt> will never return if it does not first issue a <tt>wr.close</tt>.
- !ruby/struct:SM::Flow::VERB 
 body: " rd, wr = IO.pipe\n\n if fork\n wr.close\n puts &quot;Parent got: &lt;#{rd.read}&gt;&quot;\n rd.close\n Process.wait\n else\n rd.close\n puts &quot;Sending message to parent&quot;\n wr.write &quot;Hi Dad&quot;\n wr.close\n end\n"
- !ruby/struct:SM::Flow::P 
 body: produces:
- !ruby/struct:SM::Flow::VERB 
 body: " Sending message to parent\n Parent got: &lt;Hi Dad&gt;\n"
full_name: IO::pipe
is_singleton: true
name: pipe
params: |
 IO.pipe -> array

visibility: public

Back