Well, all you'd need in a Python errorchecker like that, is to (a) make it
mandatory for the programmer "declare" member variables, then (b) parse the code
and print a warning if you use an undeclared variable. (There are other kinds of
programming errors too, of course.) Maybe such a thing exists
On Tue, Mar 14, 2006 at 03:26:28PM +0800, Lalo Martins wrote:
> Not really... you can *emulate* dynamic typing on a more static language
> like C++, but you only get dynamic typing between subclasses of a given
> root point (RefCounted in the case of VOS, IIRC). In fact, vRef is one
> of the best
Lalo,
On 3/14/06, Lalo Martins <[EMAIL PROTECTED]> wrote:
And you can constrain even that using slots. If you're interested,contact me in private :-) otherwise, just record the fact that it's
possible. (A class with slots makes all attribute assignments failunless the attribute name is in the slo
And so says Peter Amstutz on 14/03/06 14:23...
> That said, there's probably a crossing-over point, where projects
> below some size are better served with a dynamic type system, and
> projects above that size are better server with a static type system.
> The point could also be made that certain
And so says Hugh Perkins on 13/03/06 19:14...
> Lalo,
>
> What are your thoughts on Duck Typing? http://boo.codehaus.org/Duck+Typing
that's how I work most of the time :-) in the company where I used to
work, we had an expression going around, "Beijing Duck Typing"...
best,
And so says Hugh Perkins on 13/03/06 18:59...
> I guess the thing that I find tricky in Python is that it is possible to
> accidentally add unintended properties to a class by misspelling the
> intended one, and sometimes it's tricky to catch this.
It is certainly possible, but it doesn't happen a
