java.lang.Object
java.lang.System
The
System
class contains several useful class fields and methods. It cannot be instantiated.
Among the facilities provided by the
System
class are standard input, standard output, and error output streams; access to externally defined properties and environment variables; a means of loading files and libraries; and a utility method for quickly copying a portion of an array.Field Summary | ||
---|---|---|
public static final InputStream | in | The “standard” input stream. This stream is already open and ready to supply input data. Typically this stream corresponds to keyboard input or another input source specified by the host environment or user. |
public static final PrintStream | out | The “standard” output stream. This stream is already open and ready to accept output data. Typically this stream corresponds to display output or another output destination specified by the host environment or user.For simple stand-alone Java applications, a typical way to write a line of output data is:
See the
println methods in class PrintStream .
Also see:
java.io.PrintStream#println()java.io.PrintStream#println(boolean)java.io.PrintStream#println(char)java.io.PrintStream#println(char[])java.io.PrintStream#println(double)java.io.PrintStream#println(float)java.io.PrintStream#println(int)java.io.PrintStream#println(long)java.io.PrintStream#println(java.lang.Object)java.io.PrintStream#println(java.lang.String) |
public static final PrintStream | err | The “standard” error output stream. This stream is already open and ready to accept output data.Typically this stream corresponds to display output or another output destination specified by the host environment or user. By convention, this output stream is used to display error messages or other information that should come to the immediate attention of a user even if the principal output stream, the value of the variable out , has been redirected to a file or other destination that is typically not continuously monitored. |
Method from java.lang.System Detail: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
src
dest
length
srcPos
srcPos+length-1
destPos
destPos+length-1
If the
src and dest arguments refer to the same array object, then the copying is performed as if the components at positions srcPos through srcPos+length-1 were first copied to a temporary array with length components and then the contents of the temporary array were copied into positions destPos throughdestPos+length-1 of the destination array.
If
dest is null , then a NullPointerException is thrown.
If
src is null , then a NullPointerException is thrown and the destination array is not modified.
Otherwise, if any of the following is true, an
ArrayStoreException is thrown and the destination is not modified:
Otherwise, if any of the following is true, an
IndexOutOfBoundsException is thrown and the destination is not modified:
Otherwise, if any actual component of the source array from position
srcPos through srcPos+length-1 cannot be converted to the component type of the destination array by assignment conversion, an ArrayStoreException is thrown. In this case, let k be the smallest nonnegative integer less than length such thatsrc[srcPos+ k] cannot be converted to the component type of the destination array; when the exception is thrown, source array components from positionssrcPos through srcPos+ k-1 will already have been copied to destination array positions destPos through destPos+ k-1 and no other positions of the destination array will have been modified. (Because of the restrictions already itemized, this paragraph effectively applies only to the situation where both arrays have component types that are reference types.) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if a security manager exists, its
SecurityManager.checkPermission method is called with a PropertyPermission(key, "write") permission. This may result in a SecurityException being thrown. If no exception is thrown, the specified property is removed. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See the description of the class
Date for a discussion of slight discrepancies that may arise between “computer time” and coordinated universal time (UTC). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This method calls the
exit method in class Runtime . This method never returns normally.
The call
System.exit(n) is effectively equivalent to the call:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Calling the
gc method suggests that the Java Virtual Machine expend effort toward recycling unused objects in order to make the memory they currently occupy available for quick reuse. When control returns from the method call, the Java Virtual Machine has made a best effort to reclaim space from all discarded objects.
The call
System.gc() is effectively equivalent to the call:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if there is a security manager, its
checkPropertiesAccess method is called with no arguments. This may result in a security exception.
The current set of system properties for use by the #getProperty(String) method is returned as a
Properties object. If there is no current set of system properties, a set of system properties is first created and initialized. This set of system properties always includes values for the following keys:
Multiple paths in a system property value are separated by the path separator character of the platform.
Note that even if the security manager does not permit the
getProperties operation, it may choose to permit the #getProperty(String) operation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if there is a security manager, its
checkPropertyAccess method is called with the key as its argument. This may result in a SecurityException.
If there is no current set of system properties, a set of system properties is first created and initialized in the same manner as for the
getProperties method. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if there is a security manager, its
checkPropertyAccess method is called with the key as its argument.
If there is no current set of system properties, a set of system properties is first created and initialized in the same manner as for the
getProperties method. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If the system does not support environment variables, an empty map is returned.
The returned map will never contain null keys or values. Attempting to query the presence of a null key or value will throw a NullPointerException . Attempting to query the presence of a key or value which is not of type String will throw aClassCastException .
The returned map and its collection views may not obey the general contract of the Object#equals and Object#hashCode methods.
The returned map is typically case-sensitive on all platforms.
If a security manager exists, its checkPermission method is called with a
RuntimePermission ("getenv.*") permission. This may result in aSecurityException being thrown.
When passing information to a Java subprocess, system properties are generally preferred over environment variables.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If a security manager exists, its checkPermission method is called with a
RuntimePermission ("getenv."+name) permission. This may result in aSecurityException being thrown. If no exception is thrown the value of the variable name is returned.
System properties and environment variables are both conceptually mappings between names and values. Both mechanisms can be used to pass user-defined information to a Java process. Environment variables have a more global effect, because they are visible to all descendants of the process which defines them, not just the immediate Java subprocess. They can have subtly different semantics, such as case insensitivity, on different operating systems. For these reasons, environment variables are more likely to have unintended side effects. It is best to use system properties where possible. Environment variables should be used when a global effect is desired, or when an external system interface requires an environment variable (such as
PATH ).
On UNIX systems the alphabetic case of
name is typically significant, while on Microsoft Windows systems it is typically not. For example, the expressionSystem.getenv("FOO").equals(System.getenv("foo")) is likely to be true on Microsoft Windows. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This method returns the channel obtained by invoking the inheritedChannelmethod of the system-wide default java.nio.channels.spi.SelectorProvider object.
In addition to the network-oriented channels described in inheritedChannel , this method may return other kinds of channels in the future.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
On UNIX systems, it returns {@code “\n”}; on Microsoft Windows systems it returns {@code “\r\n”}.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The call
System.load(name) is effectively equivalent to the call:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
libname
The call
System.loadLibrary(name) is effectively equivalent to the call
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This method can only be used to measure elapsed time and is not related to any other notion of system or wall-clock time. The value returned represents nanoseconds since some fixed but arbitrary origin time (perhaps in the future, so values may be negative). The same origin is used by all invocations of this method in an instance of a Java virtual machine; other virtual machine instances are likely to use a different origin.
This method provides nanosecond precision, but not necessarily nanosecond resolution (that is, how frequently the value changes) – no guarantees are made except that the resolution is at least as good as that of #currentTimeMillis() .
Differences in successive calls that span greater than approximately 292 years (263 nanoseconds) will not correctly compute elapsed time due to numerical overflow.
The values returned by this method become meaningful only when the difference between two such values, obtained within the same instance of a Java virtual machine, is computed.
For example, to measure how long some code takes to execute:
{@code
long startTime = System.nanoTime();
// ... the code being measured ...
long estimatedTime = System.nanoTime() - startTime;}
To compare two nanoTime values
{@code
long t0 = System.nanoTime();
...
long t1 = System.nanoTime();}
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Calling this method suggests that the Java Virtual Machine expend effort toward running the
finalize methods of objects that have been found to be discarded but whose finalize methods have not yet been run. When control returns from the method call, the Java Virtual Machine has made a best effort to complete all outstanding finalizations.
The call
System.runFinalization() is effectively equivalent to the call:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deprecated!
This – method is inherently unsafe. It may result in finalizers being called on live objects while other threads are concurrently manipulating those objects, resulting in erratic behavior or deadlock.
If there is a security manager, its
checkExit method is first called with 0 as its argument to ensure the exit is allowed. This could result in a SecurityException. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if there is a security manager, its
checkPermission method is called with aRuntimePermission("setIO") permission to see if it’s ok to reassign the “standard” error output stream. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if there is a security manager, its
checkPermission method is called with aRuntimePermission("setIO") permission to see if it’s ok to reassign the “standard” input stream. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if there is a security manager, its
checkPermission method is called with aRuntimePermission("setIO") permission to see if it’s ok to reassign the “standard” output stream. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Properties
First, if there is a security manager, its
checkPropertiesAccess method is called with no arguments. This may result in a security exception.
The argument becomes the current set of system properties for use by the#getProperty(String) method. If the argument is
null , then the current set of system properties is forgotten. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
First, if a security manager exists, its
SecurityManager.checkPermission method is called with a PropertyPermission(key, "write") permission. This may result in a SecurityException being thrown. If no exception is thrown, the specified property is set to the given value. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If there is a security manager already installed, this method first calls the security manager’s
checkPermission method with aRuntimePermission("setSecurityManager") permission to ensure it’s ok to replace the existing security manager. This may result in throwing aSecurityException .
Otherwise, the argument is established as the current security manager. If the argument is
null and no security manager has been established, then no action is taken and the method simply returns. |
No comments:
Post a Comment