dk.brics.string
Class AnalyzeRuntime

java.lang.Object
  dk.brics.string.AnalyzeRuntime

public class AnalyzeRuntime
extends Object

An executable front-end for analyzing programs using the string analysis runtime library.

The given classes are analyzed using the string analysis, and the results are compared to the expected results as given in all Strings.analyze and Strings.check calls.

For all Strings.analyze calls, there are three cases:

• The inferred language is identical to the expected language.
  The message "Exact match!" is printed.
• The inferred language is a subset of the expected language.
  The message "Always satisfied!" is printed.
• There exist one or more strings in the inferred language that are not in the expected language.
  One shortest example of such a string is printed.

For all Strings.check calls, there are also three cases:

• The inferred language is a subset of the expected language, indicating that the check always succeeds.
  The message "Always satisfied!" is printed.
• The inferred language is disjoint from the expected language, indicating that the check always fails.
  The message "Never satisfied!" is printed.
• Otherwise, nothing is printed.

Method Summary

static void	main(String[] args) Main method for the runtime system.
static void	setupLogger() Initializes the log4j system to print all messages from AnalyzeRuntime in System.out, and suppress all other non-error messages.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Detail

main

public static void main(String[] args)
                 throws IOException,
                        IllegalAccessException,
                        InstantiationException

Main method for the runtime system.

Any number of arguments may be given. The types of arguments are:

• -dir=directory or jar
  Use all class files found in the specified jar file or directory (and its subdirectories, recursively) as application classes. The directory must refer to the root package. The directory or jar file does not have to be on the classpath.
• classname
  Use the class with the specified fully qualified name or filename as an application class. The class must be on the classpath.
• -lib=directory or jar
  Add every jar file in the specified directory to the classpath, or just the specified file if a jar file was specified. This will typically point to the analyzed project's lib directory.
• -resolver=classname
  Use the class with the specified fully qualified name or filename as a resolver in the analysis. The class must be on the classpath. It must have a constructor taking no arguments and it must implement the Resolver interface.
• -externalvisibility=classname or a special identifier
  Use the class with the specified fully qualified name or filename as a resolver in the analysis. The class must be on the classpath. It must have a constructor taking no arguments and it must implement the Resolver interface. Instead of a classname, one may specify one of the predefined strategies using the identifier public or main, which are shorthands for PublicExternalVisibility and MainExternalVisibility, respectively.

Parameters:

args - a list of arguments, as described above

Throws:

IOException

IllegalAccessException

InstantiationException

setupLogger

public static void setupLogger()

Initializes the log4j system to print all messages from AnalyzeRuntime in System.out, and suppress all other non-error messages.