Toggle personal menu
From triplescripts.org wiki
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
fill this in!
The '''SystemA''' design pattern is one of the recommended ways to implement the [[system]] layers that a program relies on and provides an elegant way to initialize those layers from within the [[shunting block]]. Conventions: * ''SystemA'' - both the name of the design pattern and a way to emphasize that the system interface should be both abstracted away from the heart of the program and be well-defined * ''SystemB'' - the implementation of the system interface that allows the program to run in the browser * ''SystemC'' - the implementation of the system interface that allows the program to run in the terminal as a command-line application The idea is that executing the [[shunting block]] will result in one of <code>SystemB</code> or <code>SystemC</code> being instantiated, which the heart of the program can rely on as a [[capabilities]] provider. == See also == * [[abstract system interface]] * [[shunting]]
Please note that all contributions to triplescripts.org wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
(opens in new window)
Retrieved from "