From: Ricardo Wurmus <rekado@elephly.net>
To: 27132@debbugs.gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>
Subject: bug#27132: [PATCH 3/6] gnu: Add sbcl-parse-number.
Date: Mon, 29 May 2017 19:21:28 +0200 [thread overview]
Message-ID: <20170529172131.20954-3-rekado@elephly.net> (raw)
In-Reply-To: <20170529172131.20954-1-rekado@elephly.net>
* gnu/packages/lisp.scm (sbcl-parse-number): New variable.
---
gnu/packages/lisp.scm | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index 473c31f39..240c1b27f 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -1249,3 +1249,27 @@ multiple inspectors with independent history.")
(description "Parse-js is a Common Lisp package for parsing
JavaScript (ECMAScript 3). It has basic support for ECMAScript 5.")
(license license:zlib))))
+
+(define-public sbcl-parse-number
+ (package
+ (name "sbcl-parse-number")
+ (version "1.5")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (string-append "https://github.com/sharplispers/parse-number/"
+ "archive/v" version ".tar.gz"))
+ (file-name (string-append name "-" version ".tar.gz"))
+ (sha256
+ (base32
+ "1k6s4v65ksc1j5i0dprvzfvj213v6nah7i0rgd0726ngfjisj9ir"))))
+ (build-system asdf-build-system/sbcl)
+ (home-page "http://www.cliki.net/PARSE-NUMBER")
+ (synopsis "Parse numbers")
+ (description "@code{parse-number} is a library of functions for parsing
+strings into one of the standard Common Lisp number types without using the
+reader. @code{parse-number} accepts an arbitrary string and attempts to parse
+the string into one of the standard Common Lisp number types, if possible, or
+else @code{parse-number} signals an error of type @code{invalid-number}.")
+ (license license:bsd-3)))
+
--
2.12.2
next prev parent reply other threads:[~2017-05-29 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 16:53 bug#27132: [PATCH 0/6] Add uglify-js Ricardo Wurmus
2017-05-29 17:21 ` bug#27132: [PATCH 1/6] gnu: Add sbcl-cl-ppcre-unicode Ricardo Wurmus
2017-05-29 17:21 ` bug#27132: [PATCH 2/6] gnu: Add sbcl-parse-js Ricardo Wurmus
2017-06-01 12:00 ` Ludovic Courtès
2017-05-29 17:21 ` Ricardo Wurmus [this message]
2017-06-01 12:01 ` bug#27132: [PATCH 3/6] gnu: Add sbcl-parse-number Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 4/6] gnu: Add sbcl-iterate Ricardo Wurmus
2017-06-01 12:01 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 5/6] gnu: Add sbcl-cl-uglify-js Ricardo Wurmus
2017-06-01 12:02 ` Ludovic Courtès
2017-05-29 17:21 ` bug#27132: [PATCH 6/6] gnu: Add uglify-js Ricardo Wurmus
2017-06-01 12:03 ` Ludovic Courtès
2017-06-01 21:33 ` Ricardo Wurmus
2017-06-02 19:00 ` Arun Isaac
2017-06-01 12:00 ` bug#27132: [PATCH 1/6] gnu: Add sbcl-cl-ppcre-unicode Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170529172131.20954-3-rekado@elephly.net \
--to=rekado@elephly.net \
--cc=27132@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.