International Journal of Soft Computing
ISSN: OnlineISSN: Print 1816-9503
Abstract
Today, it is not uncommon for software teachers to recommend that no function or method should be longer than a few lines. A few decades ago, the recommendation was the opposite: Don’t put something in a separate subroutine if it is only called once. The reasons for this shift in software writing style are that mathematical projects have become bigger and more complex, that there is more focus on the costs of software development and that computers have become more powerful. The high priority of structured software development and the low priority of program efficiency are reflected, first and foremost, in the choice of programming language and interface frameworks. This study explores these considerations.
How to cite this article:
Kostas Zotos . Exloring Mathematical Software.
DOI: https://doi.org/10.36478/ijscomp.2007.595.598
URL: https://www.makhillpublications.co/view-article/1816-9503/ijscomp.2007.595.598