Information for RPM apache-commons-javaflow-1.0-0.11.20120509SNAPSHOT.fc24.src.rpm
| ID | 588 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | apache-commons-javaflow | |||||||||||||||
| Version | 1.0 | |||||||||||||||
| Release | 0.11.20120509SNAPSHOT.fc24 | |||||||||||||||
| Epoch | ||||||||||||||||
| Arch | src | |||||||||||||||
| Summary | Commons Javaflow | |||||||||||||||
| Description | Sometimes it is useful if we can capture the state of the application, its stack of function calls, which includes local variables, the global variables and the program counter, and save them into an object. If this object would give us the ability to restart the processing from the point stored in it. A continuation is exactly the type of object that we need. Think of a continuation as an object that, for a given point in your program, contains a snapshot of the stack trace, including all the local variables, and the program counter. You can not only store these things in the continuation object, but also restore the execution of the program from a continuation object. This means that the stack trace and the program counter of the running program become the ones stored in a continuation. Continuations are powerful concepts from the world of functional languages, like Scheme, but they are becoming popular in other languages as well. | |||||||||||||||
| Build Time | 2016-02-03 16:58:42 GMT | |||||||||||||||
| Size | 109.25 KB | |||||||||||||||
| ce17e78bbc7280f6f7e62f424ab3e321 | ||||||||||||||||
| License | ASL 2.0 | |||||||||||||||
| Provides | No Provides | |||||||||||||||
| Obsoletes | No Obsoletes | |||||||||||||||
| Conflicts | No Conflicts | |||||||||||||||
| Requires |
|
|||||||||||||||
| Recommends | No Recommends | |||||||||||||||
| Suggests | No Suggests | |||||||||||||||
| Supplements | No Supplements | |||||||||||||||
| Enhances | No Enhances | |||||||||||||||
| Files |
|
|||||||||||||||
| Component of | No Buildroots | |||||||||||||||
