<br><div class="gmail_quote">On Fri, Apr 1, 2011 at 10:00 AM, Stefan Behnel <span dir="ltr"><<a href="mailto:stefan_ml@behnel.de">stefan_ml@behnel.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Nobody, 01.04.2011 18:52:<div class="im"><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Java is a statically-typed language which makes a distinction between<br>
primitive types (bool, int, double, etc) and objects. Python is a<br>
dynamically-typed language which makes no such distinction. Even something<br>
as simple as "a + b" can be a primitive addition, a bigint addition, a<br>
call to a.__add__(b) or a call to b.__radd__(a), depending upon the values<br>
of a and b (which can differ for different invocations of the same code).<br>
<br>
This is one of the main reasons that statically-typed languages exist, and<br>
are used for most production software.<br>
</blockquote>
<br></div>
I doubt that the reason they are "used for most production software" is a technical one.<br><font color="#888888">
<br></font></blockquote><div>Agreed.<br><br>In school, I was taught by a VHDL expert that the distinction between what gets done in hardware and what gets down in software is largely arbitrary - other than hardware often being faster than software, and hardware being less mutable than software.<br>
<br>Lisp machines exist, or at least did at one time - from there, a Python machine doesn't seem much of stretch.<br><br></div></div>