Results for: "fnmatch"

@private

Raised when trying to use a canceled tuple.

Templates are used to match tuples in Rinda.

Documentation?

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]]

Some tags must only exist a specific number of times in a given RSS feed. If a feed has too many occurrences of one of these tags, a TooMuchTagError will be raised.

Certain attributes are required on specific tags in an RSS feed. If a feed is missing one of these attributes, a MissingAttributeError is raised.

Raised when an unknown conversion error occurs.

Raised when a RSS::Maker attempts to use an unknown maker.

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

Base class for all Gem commands. When creating a new gem command, define initialize, execute, arguments, defaults_str, description and usage (as appropriate). See the above mentioned methods for details.

A very good example to look at is Gem::Commands::ContentsCommand

No documentation available

Potentially raised when a specification is validated.

No documentation available
No documentation available
No documentation available

Raised by Gem::Validator when something is not right in a gem.

Raised by Resolver when a dependency requests a gem for which there is no spec.

A test case for Gem::Installer.

Gem::PathSupport facilitates the GEM_HOME and GEM_PATH environment settings to the rest of RubyGems.

No documentation available

Gem::StubSpecification reads the stub: line from the gemspec. This prevents us having to eval the entire gemspec in order to find out certain information.

RubyGemTestCase provides a variety of methods for testing rubygems and gem-related behavior in a sandbox. Through RubyGemTestCase you can install and uninstall gems, fetch remote gems through a stub fetcher and be assured your normal set of gems is not affected.

Tests are always run at a safe level of 1.

Search took: 4ms  ·  Total Results: 2158