On Sat, Jul 5, 2014 at 10:10 AM, Matt Oliveri <[email protected]> wrote: > On Sat, Jul 5, 2014 at 9:47 AM, Sandro Magi <[email protected]> wrote:
>> It seems clear that no subprogram written against ROFile can write to an >> underlying file, even when given an RWFile, no matter what other >> subprograms it may call to do its job. > > Assuming all those methods are public, this is technically incorrect, > because reflection would allow calling the RWFile's Write method > regardless of the static type. > Without reflection or downcast, you're right. In OCaml, you're right. > Taking away reflection results in an object system with a very different feel. > Without reflection, I'd agree that Shap's point of view is more > natural, and that ambient promiscuous downcast should probably be > omitted too. But I believe Java was intentionally trying to make my > kind of object system, not Shap's kind. fwiw I recall the following which is a buffet of reflection mishaps, including one that looks an awful lot like a classic confused deputy #636312 http://www.cert.org/blogs/certcc/post.cfm?EntryID=136 _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
