Taming of Pict

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Friends,

During the summer, I have posted a lightweight article about taming of Pict (turning Pict into a
proper object-capability language) and to a nearby conference (SOFSEM).

(paper)
http://altair.sk:60001/mediawiki/upload/d/de/Sofsem2008.pdf

(slides)
http://altair.sk:60001/mediawiki/upload/6/65/Sofsem2008-presentation.beamer.pdf

(prepared talk)
http://altair.sk:60001/mediawiki/upload/4/4b/Sofsem2008-presentation.article.pdf

The talk is already over. It did not go to detail about the language (there was not much time) but
hopefully covered usefullness object-capabilities.

The open problem were not solved yet (related to possibilities of untrusted components to waste as
much memory and as much CPU without proper bounds). As soon as I complete boring commercial Erlang
project, I will try tackle that. I believe they are solvable. The question is only the price---how
much will TCB grow and how much flexible mechanisms for constraining "memory consumption" and "CPU
consumption" will be available.

Two people helped me:
- - Frank Piessens (as a shepherd helped me a lot with turning "conditionally accepted" paper to
"accepted")
- - Norman Hardy (helped me filter out some errors I was not able to recognize)
I am grateful to both of them.

Best regards,
- --
Matej Kosik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHmMG2L+CaXfJI/hgRAno1AKCPIcjR3D0vodIFkowcN8aQ1jze+ACg2SA2
DmmOq80j+LNTvi9gOQxPt9s=
=Rk7h
-----END PGP SIGNATURE-----