Computer science

From Trek DB
Revision as of 16:55, 30 May 2019 by Idran (talk | contribs)
Jump to navigation Jump to search
  • 24th century computer programming seemingly built modularly rather than low-level coding for 99% of design
    • Individual modules known as "subroutines", hard-built functions with specific input and output hooks
    • Can be individually enabled/disabled
      • When disabled, message-passing simply passes through rather than interrupting program flow
    • Manipulating functionality of an existing program thus consists of adding, deleting, enabling, or disabling individual subroutines rather than engaging in raw code
      • Possibly a factor of code density and/or safety? By using individual, expansively complex modules that have been formally verified, code errors can be reduced to a minimum
      • New subroutines could still be designed as needed (and described), inserted, but with potentially less effectiveness or errors
      • On many occasions, due to complexity of overall system, individual subroutines will be installed on individual removable storage elements, allowing for quick coding of new subroutines to replace existing in order to modify overall functioning (TNG: "The Naked Now")