Results for: "Pathname"

ReadTimeout, a subclass of Timeout::Error, is raised if a chunk of the response cannot be read within the read_timeout.

WriteTimeout, a subclass of Timeout::Error, is raised if a chunk of the response cannot be written within the write_timeout. Not raised on Windows.

Base class of exceptions from OptionParser.

Raises when ambiguously completable string is encountered.

Raises when there is an argument for a switch which takes no argument.

Raises when a switch with mandatory argument has no argument.

Raises when the given argument does not match required format.

No documentation available

A set of rule and position in it’s RHS. Note that the number of pointers is more than rule’s RHS array, because pointer points right edge of the final symbol when reducing.

No documentation available
No documentation available
No documentation available

A table of LALR states.

A LALR state.

No documentation available

Indicates a timeout resolving a name or address.

Templates are used to match tuples in Rinda.

Documentation?

TupleSpaceProxy allows a remote Tuplespace to appear as local.

A TemplateEntry is a Template together with expiry and cancellation data.

Documentation?

A NotifyTemplateEntry is returned by TupleSpace#notify and is notified of TupleSpace changes. You may receive either your subscribed event or the ‘close’ event when iterating over notifications.

See TupleSpace#notify_event for valid notification types.

Example

ts = Rinda::TupleSpace.new
observer = ts.notify 'write', [nil]

Thread.start do
  observer.each { |t| p t }
end

3.times { |i| ts.write [i] }

Outputs:

['write', [0]]
['write', [1]]
['write', [2]]

The Tuplespace manages access to the tuples it contains, ensuring mutual exclusion requirements are met.

The sec option for the write, take, move, read and notify methods may either be a number of seconds or a Renewer object.

BasicSpecification is an abstract class which implements some common code used by both Specification and StubSpecification.

The command manager registers and installs all the individual sub-commands supported by the gem command.

Extra commands can be provided by writing a rubygems_plugin.rb file in an installed gem. You should register your command against the Gem::CommandManager instance, like this:

# file rubygems_plugin.rb
require 'rubygems/command_manager'

Gem::CommandManager.instance.register_command :edit

You should put the implementation of your command in rubygems/commands.

# file rubygems/commands/edit_command.rb
class Gem::Commands::EditCommand < Gem::Command
  # ...
end

See Gem::Command for instructions on writing gem commands.

Search took: 2ms  ·  Total Results: 2267