Package jut.lang

utilities related to the java.lang package, taken from the java utility classes collection "jut".

See:
          Description

Interface Summary
OneTimeIterable<T> special purpose restricted version of the Iterable interface. the OneTimeIterable.iterator() method classes implementing this interface may only be called once, subsequent calls should throw an exception.
ParamCallable<S,T> interface providing a common protocol for objects that wish to execute code with one parameter and return a result to the caller.
ParamRunnable<T> interface providing a common protocol for objects that wish to execute code with one parameter.
 

Class Summary
AbstractOneTimeIterable<T> template implementation of OneTimeIterable. the iterator of this template does not support the Iterator.remove() method. as convenience, a user method can be called before handing over the result of Iterator.next(), see AbstractOneTimeIterable.onNext(jut.lang.ParamRunnable).
Assertions static assertions utility methods.
Lists static utility methods for lists, enumeration, iterations and so on.
OneTimeIterableWrapper<T> wrapper for an Iterable to guarantee only one Iterator can be obtained. as convenience, a user method can be called before handing over the result of Iterator.next(), see AbstractOneTimeIterable.onNext(jut.lang.ParamRunnable).
Strings static string utility methods.
 

Exception Summary
NestedException wrapper class for wrapping a Throwable in a RuntimeException. the main use for this is to wrap declared exceptions in interface implementations that do not declare exceptions themselves, like Runnable. as far as possible, a NestedException exposes the properties of the wrapped Throwable.
 

Package jut.lang Description

utilities related to the java.lang package, taken from the java utility classes collection "jut". "jut" is a collection of utility classes for Java that covers mostly simple things that the standard JDK just doesn't offer.

copyright (C) 2003-2009 Georg Dietrich

this utilities collection is designed along the following guidelines:

  1. the API should be well documented, easy to use, and the code should contain few bugs.
  2. the API should be stable and as flexible as possible while keeping the source code easily maintainable.