[cap-talk] C-like Capability language

Jonathan S. Shapiro shap at eros-os.com
Tue Aug 5 09:48:10 CDT 2008


On Tue, 2008-08-05 at 14:10 +1000, James A. Donald wrote:

> Bytecode has significant performance costs.

That has certainly been true in many implementations. For the type of
bytecode and method of use that I have in mind for BitC, there is no
reason why the overhead should exceed 1.5%. Since the intended use of
bytecode is a fall-back for those portions of the code that cannot be
natively compiled in advance, I suspect that this will be more than
acceptable.

> Plus there is a huge amount of software in C, most of it
> woefully insecure, that is *not* going to move to a
> managed code environment.

I'm not convinced of this, but I will address this in a separate note.



More information about the cap-talk mailing list