StdFileStream.close - multiple declarations
- Function StdFileStream.close
- Function StdFileStream.close
- Function StdFileStream.close
- Function StdFileStream.close
Function StdFileStream.close
Actively closes the connection and frees associated resources.
Note that close
must always be called, even if the remote has already
closed the connection. Failure to do so will result in resource and
memory leakage.
Closing a connection implies a call to finalize
, so that it doesn't
need to be called explicitly (it will be a no-op in that case).
Prototype
override void close();
Function StdFileStream.close
Actively closes the connection and frees associated resources.
Note that close
must always be called, even if the remote has already
closed the connection. Failure to do so will result in resource and
memory leakage.
Closing a connection implies a call to finalize
, so that it doesn't
need to be called explicitly (it will be a no-op in that case).
Prototype
override void close();
Function StdFileStream.close
Actively closes the connection and frees associated resources.
Note that close
must always be called, even if the remote has already
closed the connection. Failure to do so will result in resource and
memory leakage.
Closing a connection implies a call to finalize
, so that it doesn't
need to be called explicitly (it will be a no-op in that case).
Prototype
override void close();
Function StdFileStream.close
Actively closes the connection and frees associated resources.
Note that close
must always be called, even if the remote has already
closed the connection. Failure to do so will result in resource and
memory leakage.
Closing a connection implies a call to finalize
, so that it doesn't
need to be called explicitly (it will be a no-op in that case).
Prototype
override void close();
Authors
Sönke Ludwig, Eric Cornelius
Copyright
© 2014 RejectedSoftware e.K.
License
Subject to the terms of the MIT license, as written in the included LICENSE.txt file.