On Thu, 28 Aug 2003 15:10:33 +0200
Anders Arnholm <anders@arnholm.nu> wrote:
> One of the main reasons is that Python leaves a loot of the resolving to
> runtime, that means that the code actually has to be run before you can
> see tha actuall typo found at compile time in languanges as C.
This is offset by the fact that the code-compile-run cycle is reduced to
code-run. Furthermore a lot of prototyping of code can be done interactively.
When I run into a situation where I'm not sure exactly how I want to do
something I open another window, fire up Python, import the appropriate
libraries and twiddle with the code until I get a form that works. Then I
take that and put it back into the main code.
--
Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
PGP Key: 8B6E99C5 | main connection to the switchboard of souls.
-------------------------------+---------------------------------------------
Attachment:
pgpI3S_Ryh4d1.pgp
Description: PGP signature