Results for: "remove_const"

Represents a YAML stream. This is the root node for any YAML parse tree. This node must have one or more child nodes. The only valid child node for a Psych::Nodes::Stream node is Psych::Nodes::Document.

No documentation available

File-based session storage class.

Implements session storage as a flat file of ‘key=value’ values. This storage type only works directly with String values; the user is responsible for converting other types to Strings when storing and from Strings when retrieving.

Dummy session storage class.

Implements session storage place holder. No actual storage will be done.

PStore-based session storage class.

This builds upon the top-level PStore class provided by the library file pstore.rb. Session data is marshalled and stored in a file. File locking and transaction services are provided.

Tokens where state should be ignored used for :on_comment, :on_heredoc_end, :on_embexpr_end

No documentation available
No documentation available
No documentation available

Used Internally. Wraps a Dependency object to also track which spec contained the Dependency.

A VendorSpecification represents a gem that has been unpacked into a project and is being loaded through a gem dependencies file through the path: option.

For detail, see the MSDN.

— HKEY_*

Predefined key ((*handle*)).
These are Integer, not Win32::Registry.

— REG_*

Registry value type.

— KEY_*

Security access mask.

— KEY_OPTIONS_*

Key options.

REG_CREATED_NEW_KEY

REG_OPENED_EXISTING_KEY

If the key is created newly or opened existing key.
See also Registry#disposition method.

Converts Ruby link flags into something cargo understands

No documentation available
No documentation available
No documentation available
No documentation available
No documentation available

Indicates a problem with the DNS request.

No documentation available

IO wrapper that allows writing a limited amount of data

No documentation available
No documentation available

Continuation objects are generated by Kernel#callcc, after having +require+d continuation. They hold a return address and execution context, allowing a nonlocal return to the end of the callcc block from anywhere within a program. Continuations are somewhat analogous to a structured version of C’s setjmp/longjmp (although they contain more state, so you might consider them closer to threads).

For instance:

require "continuation"
arr = [ "Freddie", "Herbie", "Ron", "Max", "Ringo" ]
callcc{|cc| $cc = cc}
puts(message = arr.shift)
$cc.call unless message =~ /Max/

produces:

Freddie
Herbie
Ron
Max

Also you can call callcc in other methods:

require "continuation"

def g
  arr = [ "Freddie", "Herbie", "Ron", "Max", "Ringo" ]
  cc = callcc { |cc| cc }
  puts arr.shift
  return cc, arr.size
end

def f
  c, size = g
  c.call(c) if size > 1
end

f

This (somewhat contrived) example allows the inner loop to abandon processing early:

require "continuation"
callcc {|cont|
  for i in 0..4
    print "#{i}: "
    for j in i*5...(i+1)*5
      cont.call() if j == 17
      printf "%3d", j
    end
  end
}
puts

produces:

0:   0  1  2  3  4
1:   5  6  7  8  9
2:  10 11 12 13 14
3:  15 16

An error class raised when dynamic parts are found while computing a constant path’s full name. For example: Foo::Bar::Baz -> does not raise because all parts of the constant path are simple constants var::Bar::Baz -> raises because the first part of the constant path is a local variable

Search took: 4ms  ·  Total Results: 3316