[Greg Wilson]
> ...
> There's also a couple of smart guys in the class who are
> wondering about CPython vs. JPython ("So this'll be safe in
> one version of the language, but not in the other?"),
Greg, people who have been exposed to Fortran (this is LANL, right <wink>?)
can't possibly have a problem with the concept of "not defined by the
standard". Don't sell these as different *versions* of the language, but as
different implementations. That's what they are. The Python *language*
doesn't define anything about the lifetime of objects. Even when CPython
grows "real GC", thanks to refcounting too you'll still be able to *rely* on
behaviors in CPython you'll see only accidentally in JPython. You do so at
your own risk, same as e.g. you rely on floating point Fortran x+y+z getting
evaluated "left to right" at your own risk (BTW, x+y+z *is* "left to right"
in Python -- maybe they'll trade that for the lack of GC promises <wink>).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4