|Possible to write compiler to Java VM? (I volunteer to summarize) firstname.lastname@example.org (Peter Seibel) (1996-01-17)|
|Re: Possible to write compiler to Java VM? email@example.com (1996-01-29)|
|Re: Possible to write compiler to Java VM? firstname.lastname@example.org (1996-01-30)|
|Safety and power in languages email@example.com (1996-02-02)|
|Re: Safety and power in languages firstname.lastname@example.org (1996-02-04)|
|Re: Safety and power in languages email@example.com (1996-02-09)|
|Re: Safety and power in languages firstname.lastname@example.org (1996-02-09)|
|Re: Safety and power in languages email@example.com (1996-02-12)|
|Re: Safety and power in languages firstname.lastname@example.org (Christian Fabre) (1996-02-13)|
|Re: Safety and power in languages email@example.com (1996-02-13)|
|Re: Safety and power in languages firstname.lastname@example.org (Darius Blasband) (1996-02-13)|
|[1 later articles]|
|From:||email@example.com (Robert A Duff)|
|Date:||4 Feb 1996 00:59:11 -0500|
|Organization:||The World Public Access UNIX, Brookline, MA|
|References:||96-01-037 96-01-116 96-01-130 96-02-026|
Steve Witham <firstname.lastname@example.org> wrote:
>Security and safety in computers are a kind of negative power: by
>allowing less, you know more about what a program will do, without
>having to know or think as much about the program.
Well, *sometimes* that's true, but in general, I disagree.
For example, Lisp feels a *lot* more flexible to me that C, despite
the fact that there are things I can't do in Lisp -- fiddling with
memory addresses at a low level. Because I'm restricted in that way,
I can freely pass pointers around in Lisp (well, *everything's* a
pointer), without worrying about dangling pointers and storage leaks.
IMHO, the "restriction" gives *more* freedom, not less.
Similarly, OOP features make a language more flexible, but you can't
have OOP without some sort of type system (you have to at least
require the programmer to say what sort of object is being created).
Return to the
Search the comp.compilers archives again.