Results for: "OptionParser"

A module responsible for deserializing parse results.

This module is used for safely loading Marshal specs from a gem. The ‘safe_load` method defined on this module is specifically designed for loading Gem specifications.

Configuration options for dumping YAML.

This is the JSON parser implemented as a C extension. It can be configured to be used by setting

JSON.parser = JSON::Ext::Parser

with the method parser= in JSON.

Class for representing HTTP method OPTIONS:

require 'net/http'
uri = URI('http://example.com')
hostname = uri.hostname # => "example.com"
req = Net::HTTP::Options.new(uri) # => #<Net::HTTP::Options OPTIONS>
res = Net::HTTP.start(hostname) do |http|
  http.request(req)
end

See Request Headers.

Properties:

• Request body: optional.

• Response body: yes.

• Safe: yes.

• Idempotent: yes.

• Cacheable: no.

Related:

• Net::HTTP#options: sends OPTIONS request, returns response object.

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

Raised when the buffer cannot be allocated for some reason, or you try to use a buffer that’s not allocated.

Raised when the query given to a pattern is either invalid Ruby syntax or is using syntax that we don’t yet support.

Specifies a Specification object that should be activated. Also contains a dependency that was used to introduce this activation.

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.

Gem::Security default exception type

SSLServer represents a TCP/IP server socket with Secure Sockets Layer.

An OpenSSL::OCSP::SingleResponse represents an OCSP SingleResponse structure, which contains the basic information of the status of the certificate.

Represents a specification retrieved via the rubygems.org API.

This is used to avoid loading the full Specification object when all we need is the name, version, and dependencies.

A GitSpecification represents a gem that is sourced from a git repository and is being loaded through a gem dependencies file through the git: option.