3 ms·
Basically perl, Python, sh/bash, and so on. Not C or C++. (Well, there's '#!/usr/local/bin/tcc -run' [1] which can do C but, you know, that's the exception to t
by cogburnd02 12y ago
Basically perl, Python, sh/bash, and so on. Not C or C++. (Well, there's '#!/usr/local/bin/tcc -run' [1] which can do C but, you know, that's the exception to the rule.) Moar here: [2]
[1] http://bellard.org/tcc/tcc-doc.html http://bellard.org/tcc/tcc-doc.html
[2] http://en.wikipedia.org/wiki/Scripting_language http://en.wikipedia.org/wiki/Scripting_language
- rubiquity 12y agoThat's insane. Perl and Python are both general purpose programming languages. This reminds me of the days Java developers used to call Ruby developers "script kiddies." So if C and C++ are the only true programming languages, we're all just script kiddies? :/
- cogburnd02 12y agoNo. I didn't say anyone was a "script kiddie." I merely stated that the manner in which Perl and Python function is different than the manner in which C and C++ function and that's enough of a difference that they belong in two categories of languages: 'scripting languages' (which are not compiled to assembly and typically require an interpreter) and 'compiled languages' (which can be compiled to assembly and typically do not require an interpreter.) Nor did I say Perl and Python aren't suitable for general purpose tasks. If you think 'using a scripting language' is the same as 'being a script kiddie,' then you're just wrong. [I don't know enough of how Java or Ruby function to say which category they belong in.]