Discrete event simulation using PL/I based general and special purpose simulation languages
WSC '81 Proceedings of the 13th conference on Winter simulation - Volume 1
WSC '85 Proceedings of the 17th conference on Winter simulation
Perspectives on simulation using GPSS
WSC '88 Proceedings of the 20th conference on Winter simulation
WSC '86 Proceedings of the 18th conference on Winter simulation
WSC '83 Proceedings of the 15th conference on Winter simulation - Volume 1
Discrete event simulation using PL/I based general and special purpose simulation languages
WSC '81 Proceedings of the 13th conference on Winter simulation - Volume 1
WSC '81 Proceedings of the 13th conference on Winter simulation - Volume 1
WSC '84 Proceedings of the 16th conference on Winter simulation
ASSE - ADA simulation support environment
WSC '82 Proceedings of the 14th conference on Winter Simulation - Volume 1
WSC '82 Proceedings of the 14th conference on Winter Simulation - Volume 2
Process-oriented simulation languages
ACM SIGSIM Simulation Digest
| Hi-index | 0.00 |
GPSS has proven to be an excellent simulation language, but was not designed to perform the logical and computational tasks of a programming language. Strategies for improvement can take one of two paths: building adequate analytic constructs into the existing GPSS language, or building GPSS-like constructs into an existing general purpose programming language. The second choice can be made easier by use of a language-building utility program to translate simulation constructs into the selected programming language. It is also simplified by the fact that some GPSS statements (such as input-output and control) may be dropped, since any good programming language will provide native facilities for these functions. Such a fusion between the constructs of a good simulation language, and those of a good programming language, provides a far more flexible system than either alone. This paper discusses PL/I GPSS, an implementation of GPSS in a PL/I environment which uses PL/I variables as transaction variables and permits use of general PL/I expressions for most GPSS statement parameters.