Summary: strong/weak typing and pointers
Steven Bethard
steven.bethard at gmail.com
Wed Nov 3 20:03:54 EST 2004
More information about the Python-list mailing list
Wed Nov 3 20:03:54 EST 2004
- Previous message (by thread): Summary: strong/weak typing and pointers
- Next message (by thread): Summary: strong/weak typing and pointers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JCM <joshway_without_spam <at> myway.com> writes: > > > Definition 1 is the definition most commonly used in Programming > > Languages literature.... However, for > > all intents and purposes, it is only applicable to statically typed > > languages; no one on the list could come up with a dyamically typed > > language that allowed bit-reinterpretation. > > Assembly language. The types of values are implied by what > instructions you use. I'm sure some people would argue that assembly language is untyped (not statically or dynamically typed) and that the operations are defined on bits, but this is definitely the best example I've seen. Thanks! Steve
- Previous message (by thread): Summary: strong/weak typing and pointers
- Next message (by thread): Summary: strong/weak typing and pointers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list