firstname.lastname@example.org (Will Duquette) writes:
> 1. I like traditional expressions and control structures.
> A C programmer can get the gist of a Fortran, BASIC, Pascal,
> Ada, or Java program without too much effort. The syntax isn't
> identical, but the basic model is much the same.
Don't know what you mean by traditional control structures, but
Smalltalk control structures don't seem too different to C in practice.
> 2. (And this is the kicker) I really dislike having my application
> and the Smalltalk library classes live in the same "space". In the
> Smalltalk system I've looked at (Smalltalk V), if I wanted to
> develop two separate applications they either needed to live in the
> same class tree, or I needed to maintain too entirely separate
> "images", which included all of the system classes. This gives me
> chills, for some reason.
> As someone on this thread has commented, OOP in Java is more like OOP
> in Smalltalk than it is OOP in C++, and I think this is true...but in
> Java, there's a nice clean separation between my code and anybody
> else's code. I like that. Again, this may be a purely psychological
> issue, but then, I program better when I'm happy. :-)
I think it's purely psychological. :-) Think of the image as an
instant compilation of your code changes. To use the same code in two
images you need to export. The equivilent in C++ is building a
library, installing the library in a common place and then linking
with it. On the whole a lot more painful for C++.