FW: First Attempt at Crypto Library

[Martin Sjögren]

--=-WopLH0j0x2SxsfoBTguQ
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

tis 2003-04-22 klockan 12.22 skrev Simon Marlow:
> Question 1: there's a comment next to 'FileFormat' which mentions that
> 'Codec' might be a more accurate name.  It seems to me that 'Codec'
> would indeed be a better choice: many of the libraries under FileFormat
> are more like pure stream-transformers than file formats, and Codec
> encompasses both.  What do people think about changing this?  (there
> aren't any other implementations of libraries under FileFormat that I'm
> aware of).
>=20
> If FileFormat became Codec, then the existing FileFormat.Encoding looks
> a bit odd.  But moving FileFormat.Encoding.Base64 up to Codec.Base64
> (similarly for FileFormat.Encoding.Yenc) would seem to make sense.
>=20
> Question 2: what should the insides of the FileFormat.Encryption (or
> Codec.Encryption) hierarchy look like?

Having worked a bit with Unicode, I associate "codec" with Unicode
encodings. Are there any plans on modules for working with Unicode
codecs? I guess Char:s are meant to be Unicode characters, but I want
functions for converting between String:s and UTF-8, UTF-16, Latin1
(lossy, there are translation tables iirc) et.c. depending on what the
user's locale says. I guess e.g. gettext takes care of output, but input
is more interesting.


/Martin
--=20
Martin Sj=F6gren
  sjogren@debian.org -- marvin@dum.chalmers.se
  GPG key: http://www.mdstud.chalmers.se/~md9ms/gpg.html
  let hello =3D "hello" : hello in putStr (unlines hello)

--=-WopLH0j0x2SxsfoBTguQ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad
	meddelandedel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+pV2uGpBPiZwE9FYRAnM9AJ9OM44ItNj4lz8+x75W1DJdR3LZWwCdELYo
QNIr41Yp8bQX/5nH7DPbMIo=
=wU0N
-----END PGP SIGNATURE-----

--=-WopLH0j0x2SxsfoBTguQ--