
I am about to update our library for BER (Basic Encoding Rules). I have read http://www.haskell.org/~simonmar/libraries/libraries.html. I think it should be called Network.BER. I don't have any strong views on licensing and it looks like BSD would cause the least problems. I assume it should be classified as experimental. I also assume it is non-portable as uses existential types and Words and Bits. I am using CVS. Could someone tell me how I get the string -- $Id: libraries.sgml,v 1.4 2001/07/05 13:52:49 simonmar Exp $ put into the recommended header (see below)? Thanks, Dominic. ------------------------------------------------------------------------------ -- Module : module-- Copyright : (c) author year -- License : license-- -- Maintainer : libraries@haskell.org | email-address -- Stability : experimental | provisional | stable -- Portability : portable | non-portable (reason(s))-- -- $Id: libraries.sgml,v 1.4 2001/07/05 13:52:49 simonmar Exp $---- Description ----------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------- Save time by using an eTicket and our Self-Service Check-in Kiosks. For more information go to http://www.britishairways.com/eservice1

I am using CVS. Could someone tell me how I get the string
-- $Id: libraries.sgml,v 1.4 2001/07/05 13:52:49 simonmar Exp $
put into the recommended header (see below)?
I'm guessing that your question is 'how do I figure out which version number, etc. to put there?' The answer is that you can leave it completely blank or use the example string because CVS will overwrite whatever you put there with the latest version, date, etc. Someone else can better answer your other questions. My personal take is: - BSD is best - if you say it is experimental, no-one will argue with you - Existential types make it non-portable. - Words and bits come from another hs library so they are only non-portable if that library is non-portable. - It is best (possible even required) to explicitly document each individual cause of non-portability even if you know of no compiler which provides X but not Y. -- Alastair Reid reid@cs.utah.edu http://www.cs.utah.edu/~reid/
participants (2)
-
Alastair Reid
-
dominic.j.steinitz@britishairways.com