Skip to Content.
Sympa Menu

coq-club - Re: [Coq-Club] Ascii module

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] Ascii module


chronological Thread 
  • From: Adam Koprowski <adam.koprowski AT gmail.com>
  • To: Pierre Letouzey <pierre.letouzey AT inria.fr>
  • Cc: AUGER Cedric <Cedric.Auger AT lri.fr>, coq-club AT inria.fr
  • Subject: Re: [Coq-Club] Ascii module
  • Date: Fri, 4 Mar 2011 10:33:42 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=jyt5haUVDD75HKXx3O4IZ0rWTZZ5N/0o3cOLA7+RTuVm6bemTFoB1HvYL8GuCW94jt H7ACY5A928ysXieAYMBLkAo8UgvZRrU59JlU88LnpfzDcAA2MaS7MR5GNoqMwWCv+azF VDzRHj+6TH59rhJLYCHBHwDkjDvs3u63SVX5E=

  Dear all,
 
By the way, what about also reforming the module String someday ? I tend
to think that having an Haskell-like vision where string = list ascii
would be nicer than the current specialized pseudo-list type. This way,
many functions could be shared between String and List. Of course,
remain to be check that we could keep the specific parsing/printing
of strings even when string = list ascii...
 If I may add my 5 cents: I used to work quite extensively with strings in Coq and indeed I found the specialized type for strings a nuisance, so the first thing I did was to re-define it as list of characters (for precisely the reason mentioned by Pierre: being able to use list functions for strings). So I give +1 to this idea :)

  Best,
  Adam

--
Adam Koprowski  [http://adam-koprowski.net]
R&D @ MLstate   [http://mlstate.com]




Archive powered by MhonArc 2.6.16.

Top of Page