picolisp 3.1.5.2-2 source package in Ubuntu
Changelog
picolisp (3.1.5.2-2) unstable; urgency=medium * Sync to tip. * debian/picolisp.install: - Include lib/phone.css - Install arch-indep files under /usr/share/picolisp * debian/source/lintian-overrides: - Override unknown architectures armel and armhf. -- Kan-Ru Chen (陳侃如) <email address hidden> Wed, 15 Jan 2014 22:59:02 +0800
Upload details
- Uploaded by:
- Kanru Chen
- Uploaded to:
- Sid
- Original maintainer:
- Kanru Chen
- Architectures:
- any-i386 any-armel any-armeb any-arm any-avr32 any-hppa any-m32r any-m68k any-mips any-mipsel any-powerpc any-s390 any-sh3 any-sh3eb any-sh4 any-sh4eb any-sparc any-armhf kopensolaris-amd64 solaris-amd64 amd64
- Section:
- lisp
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Trusty | release | universe | lisp |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
picolisp_3.1.5.2-2.dsc | 2.1 KiB | 871bfeb820fb11cda39224bdd1da285063b56c265d9cda52ae41764d6ae84784 |
picolisp_3.1.5.2.orig.tar.gz | 847.6 KiB | 077aa0c5576abfae1e27eb2ac4706baf63a095de98246f218ef82bf600e7fdcb |
picolisp_3.1.5.2-2.debian.tar.gz | 11.1 KiB | c850c05a929bb5fa5f96d4eafe73872549f06175e3116bc948990e505f388f82 |
Available diffs
- diff from 3.1.5.2-1 to 3.1.5.2-2 (10.6 KiB)
No changes file available.
Binary packages built by this source
- picolisp: Lisp interpreter and application server framework
Pico Lisp can be viewed from two different aspects: As a general
purpose programming language, and a dedicated application server
framework.
.
As a programming language, Pico Lisp provides a 1-to-1 mapping of a
clean and powerful Lisp derivate, to a simple and efficient virtual
machine. It supports persistent objects as a first class data type,
resulting in a database system of Entity/Relation classes and a
Prolog-like query language tightly integrated into the system.
.
As an application server framework, Pico Lisp provides for database
management (including multi-user synchronization, DB garbage collection
journalling and replication), web interface integrated (and generated
from) the application data model, and an application server.