RE: Process issues (was Re: Lang)

This seems reasonable in principle. There are quite a few attributes of each library module that we need to know, quite separate from the actual name and source code. Again, it begs the question of how this meta-information will be maintained. One common database for all Haskell compilers/interpreters would be ideal.
Again, I'm wary of getting into this discussion before we've sorted out some of the other issues, but I'd advocate keeping the meta-information in the source code. I have a vision of a single source tree used by all the compilers, kept in a CVS repo, with documentation generated by HaskellDoc, and meta-information in the source and hence also the docs. Cheers, Simon

I'd advocate keeping the meta-information in the source code. I have a vision of a single source tree used by all the compilers, kept in a CVS repo, with documentation generated by HaskellDoc, and meta-information in the source and hence also the docs.
It's a great vision. Yes, I'd agree that all the information should be in the source code. Tools to extract and manipulate meta-information can then be optional rather than mandatory. Regards, Malcolm
participants (2)
-
Malcolm Wallace
-
Simon Marlow