Novel Thoughts on Scripting and Languages

Tim Cargile tecargile at hotmail.com
Fri Jan 10 18:12:12 CET 2003


Martin Christensen <knightsofspamalot-factotum at gvdnet.dk> wrote in message news:<87of6r8hne.fsf at gvdnet.dk>...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> >>>>> "Terry" == Terry Hancock <hancock at anansispaceworks.com> writes:
> Terry> I think it's "scripting" if it relies heavily on external
> Terry> applications, which you call more or less directly.
> 
> I once saw a pragmatic definition to the effect that it's scripting if
> it's practical to write a one-liner (or equivalent) that'll solve a
> useful ad hoc problem.
> 
> The way most people use the word 'script' seems to indicate that it
> should be a small program that solves a small problem (not to say that
> it's of little value). Contrast this to 'application', which indicates
> larger size.
> 
> It tends to be more difficult to define what a 'scripting language'
> is, and I'm not even sure how much sense that term makes, even though
> I occasionally use the word myself. In my experience, when people talk
> about scripting languages they are thinking of one or both of two
> properties of such languages: 1) that they make writing scripts easy
> than other languages and 2) that they make writing large applications
> more difficult than in other languages.
> 
> These are purely pragmatic 'definitions'. I'm not pretending that
> they're even very clever or useful.
> 
> Martin
> 
> - -- 
> Homepage:       http://www.cs.auc.dk/~factotum/
> GPG public key: http://www.cs.auc.dk/~factotum/gpgkey.txt
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: Using Mailcrypt+GnuPG <http://www.gnupg.org>
> 
> iEYEARECAAYFAj4claUACgkQYu1fMmOQldUloACgk6pmx2KRK3ROBj/8iIuPhYK7

My first thoughts are:  Can I 'vi/view/less' it, do I have to
wait for a compile to 'run' it, how fast will it 'run',
where is the source code and how crazy is it, and do I
really want to get involved with this?  Pragmatic hings like that.

I try to use the term 'shell executable' instead of 'shell script'.
Following this, would a '*.py' with a '#!...' as the first line
be a 'python executable'?  Then would a '*.py' script without
the '#!...' and the '*.pyo' files be 'python interpretables'?

Tim



> E8MAn0cB1A6Er+GyCKUFQU6AKMYUYCp5
> =dNyJ
> -----END PGP SIGNATURE-----




More information about the Python-list mailing list