Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Dynamically evaluating OCaml code
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2004-04-14 (20:19)
From: Issac Trotts <ijtrotts@u...>
Subject: Re: [Caml-list] recompiling bytecode
On Wed, Apr 14, 2004 at 01:54:00PM -0500, John Goerzen wrote:
> On Wed, Apr 14, 2004 at 11:21:01AM -0700, Brandon J. Van Every wrote:
> Now, you should be able to infer from this that there is a productivity
> setback with Python because certain glaring errors are not caught until
> runtime.  If your program is such that it takes several minutes or hours
> of processing to be able to hit the critical section with errors, you
> can appreciate that this is not necessarily a good thing.  (It *is*
> possible to compile things to bytecode in advance in most cases with
> Python, but this is not well supported for the average programmer)
> There are also entire classes of errors that even a Python compile will
> not catch that an OCaml compile will -- such as reversing the order of
> arguments in a function call when each argument has a different type.

There is a program called pychecker that can find some type errors and
other bugs in Python programs.  It's handy.

Issac Trotts
(w) 530-757-8789

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: