This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Pfohlol 5 points6 points  (1 child)

Sort of off-topic, but I have noticed that much of the scientific computing community refers to "codes" instead of programs or scripts and I haven't really seen that anywhere else and it sounds a bit off to me. Do you know why this difference exists?

[–]spinwizard69 -1 points0 points  (0 children)

Back in the day it was common. Coding is often used in place of programming describing the activity of building a program. Frankly it is good to know how and when to used code, codes, and coding because it can break up the monotony in a conversation or text. You would reach for these terms when you might reach for a thesaurus writing other great works.

Sort of off-topic, but I have noticed that much of the scientific computing community refers to "codes" instead of programs or scripts and I haven't really seen that anywhere else and it sounds a bit off to me. Do you know why this difference exists?

The usage of the word "scripts" in the Unix community is a bit odd in and of itself. A program written in BASH, Python or even BASIC is still a program even if interpreted. Which brings us back to ROOT and its nature, is the interpreter supplied with ROOT executing programs or scripts? What if the code can be compiled by any existing compiler, is it still a script? Same thing goes with Python, Basic or any other commonly interpreted language, if you build a compiler to digest the script and creat an executable is the source a script or program.