• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

eshamster / ps-experiment / 42
98%
master: 98%

Build:
Build:
LAST BUILD BRANCH: develop
DEFAULT BRANCH: master
Ran 17 Dec 2017 09:20AM UTC
Jobs 1
Files 6
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
42

push

travis-ci

eshamster
Change to split namespace by package

Previously, Common Lisp pacage is used only for grouping variables and
functions. Then, when they are output as JavaScript code, the
namespace is not split.

This commit introduces namespace also in JavaScript code by using
closure. But some (dirty) hacks were required.

First, to refer un-exported symbols, each package has a "_internal"
member, then internal symbols can be referred as
"<package>._internal.<symbol>". In addition, to identify un-imported
symbol, ps:symbol-to-js-string is overwritten.

Second, to send type-specifier to other package, quote is removed if
it is attached to a type-specifier symbol. In Common Lisp,
type-specifier can be specified using symbol, but it is converted to
just a string by Parenscript. In other words, the information of
package is lost. So in other package, we can no longer extract the
type. To achieve this, "quote" in Parenscript is overwritten.

Note: Variable, function and type-specfier are in a same namespace in
a package unlike Common Lisp namespace.

Note: Parenscript has a namespace system. It splits namespaces by
adding prefix to all symbols in the package. But I wanted to achieve
more Common Lisp like one that has symbol importing and exporting.

621 of 633 relevant lines covered (98.1%)

0.98 hits per line

Jobs
ID Job ID Ran Files Coverage
1 42.1 (LISP=sbcl-bin/1.3.12 COVERALLS=true) 17 Dec 2017 09:20AM UTC 0
98.1
Travis Job 42.1
Source Files on build 42
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #42
  • cef5d6ec on github
  • Prev Build on develop (#33)
  • Next Build on develop (#43)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc