Re: What are OOP's Jargons and Complexities?

2005-05-24 Thread Wibble
Thats how common lisp specifies a vector. 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. (setq foo #(1 2 3)) (setq foo 1) (setq foo "Whatever") Theres no type associate

Re: What are OOP's Jargons and Complexities?

2005-05-23 Thread Wibble
Java or even C is more strongly typed than lisp or tcl which dont really have a concept of a typed variable. Lisp only does runtime type checking unless you do wierd unnatural things. I suppose ADA or Eiffel might have stronger typing than java, but I dont know those languages. I guess strong is

Re: What are OOP's Jargons and Complexities?

2005-05-23 Thread Wibble
You're point being...? I'm an old lisp hacker too, and lisp developed objects too, because they're cool and useful (Flavors & CLOS). Java has inner classes also, and nobody misses FLET & LABELS. Limiting responsiblity and enhanced type safety, as well as improved readablity are a win hands down