A thought that occurred to me after the discussion of array initialization: allowing user access to uninitialized memory opens a security hole. It would become possible to read passwords or other sensitive data out of the "uninitialized" memory, which would rule out the use of BitC for intraprocess access control setups. I think this is more than enough to kill the idea of an uninitialized allocation primitive.
Geoffrey _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
