On Sun, 11 Dec 2005, Tomasz Zielonka wrote:

I would like to see some support in tools for enforcing such a coding
policy. It could look like this - a function written using only safe
components would be marked as safe. Every unsafe feature like FFI,
unsafePerformIO, etc. would "taint" a module/function, marking it
unsafe. You could explicitly tag module/function as trusted/reviewed/etc.
There would be different levels of trust. All this would be propagated
through the libs and program modules. A Haskell IDE could mark
safe/unsafe/trusted code with different background color, etc. You could
get statistics about the proportions of safe/unsafe/trusted code.

Btw. Modula-3 distinguishs between safe and unsafe code:
 http://research.compaq.com/SRC/m3defn/html/safety.html
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to