On Dec 30, 2006, at 5:27 PM, Mathieu Bouchard wrote:
On Thu, 28 Dec 2006, Hans-Christoph Steiner wrote:
Much more importantly, the thick coords represent that a different
data type is passing thru the coords. It's not really an issue of
representing the implementation, instead it's representing that
those two types of coords can not be intermixed.
But how does the type of those cords represent anything else than
limitations of the implementation? How does the choice of
considering those things as distinct types, and the choice to not
auto-convert between types, constitute wise design decisions,
beyond just being things that we have to accept as fact in the
context of Pd?
Its a design choice, its part of the language. Any implementation
would have to include that in order to be compatible.
.hc
_ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montréal QC Canada
------------------------------------------------------------------------
Computer science is no more related to the computer than astronomy is
related to the telescope. -Edsger Dykstra
_______________________________________________
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
