On Mon, Dec 12, 2005 at 07:20:47PM +0100, Nils Anders Danielsson wrote: > On Sun, 11 Dec 2005, Tomasz Zielonka <[EMAIL PROTECTED]> 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. > > This sounds a lot like what they have been doing in the Programatica > project.
Thanks! I'll take a look at Programatica. Best regards Tomasz -- I am searching for a programmer who is good at least in some of [Haskell, ML, C++, Linux, FreeBSD, math] for work in Warsaw, Poland _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
