Hi, My opinion is that we should include Virtual Byte String, as at least being either 1) a list of integers in [0,255] 2) a ByteString 3) a #-tuple of Virtual Byte Strings
if only because it provides a unified type for 1) and 2), so that API wanting a string of bytes can say "I accept a Virtual Byte String", and not "I accept either a list of integers in [0,255] or a ByteString". Sébastien On Mon, Jul 30, 2012 at 2:07 PM, stewart mackenzie <setor...@gmail.com>wrote: > Dear All, > > What is the outcome of the Virtual Byte String? > > Will it be included or not? > > Kind regards > Stwart >
_________________________________________________________________________________ mozart-hackers mailing list mozart-hackers@mozart-oz.org http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
