Paul Rubin http
Tue May 24 21:20:59 EDT 2005

• Previous message (by thread): What are OOP's Jargons and Complexities?
• Next message (by thread): What are OOP's Jargons and Complexities?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Wibble <Wibble at Mailinator.com> writes:
> Andreas, your link indicates that lisp is a Weakly typed language not
> strong.  Theres no compile time type semantics, at least in CommonLisp,
> MacLisp, ZetaLisp or FranzLisp.

There are runtime semantics that enforce types.

>  From your link:
>    When the types detected or declared are strictly enforced by the
>    language's semantics, the language is strongly-typed.
>    when the semantics of the language allows for inconsistencies between
>    the compile-time type and the run-time type, the language is
>    weakly-typed.

Yes, the compile-time type of 3 is integer, and the runtime type of 3
is also integer.  There is no inconsistency.  Compare that with C,
which lets you cast 3 to a pointer.

---

• Previous message (by thread): What are OOP's Jargons and Complexities?
• Next message (by thread): What are OOP's Jargons and Complexities?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list