4 ms·
>I'm not sure I understand you. You can't just start typing and getting instant feedback in Java simply because Java is not interpreted (well, actually, it is,
by Dn_Ab 16y ago
>I'm not sure I understand you. You can't just start typing and getting instant feedback in Java simply because Java is not interpreted (well, actually, it is, but you have to compile to bytecode first). So, what you're saying about Java goes for just about any compiled language.<
This is not true. There are statitically typed languages, usally functional, with a read-eval-print-loop. Haskell, Ocaml, SML, F#, Scala are the main ones I can tink of. There are many more. I will also note that your parenthetical is slightly inaccurate in that jvms usually JIT bytecode and don't just inteprete it straight.
- Sandman 16y agoAfter googling for a while, I found this great answer on SO: http://stackoverflow.com/questions/3265357/compiled-vs-interpreted-languages/3265680#3265680 http://stackoverflow.com/questions/3265357/compiled-vs-inter... Lunaryom is correct. There are no 'interpreted' and 'compiled' languages, just different implementations. So, I was wrong in my original post. It would appear that you can just type and get instant feedback in Java (if you use Beanshell, for example).
- Dn_Ab 16y agoI noticed the possibility of that semantic ambiguity, that is why I switched to noting static/dynamic typing instead of retaining your distinction on compiled/intepretated.