File: control

package info (click to toggle)
pforth 1%3A2.0.1-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, forky, sid, trixie
  • size: 904 kB
  • sloc: ansic: 6,283; makefile: 410
file content (35 lines) | stat: -rw-r--r-- 1,524 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Source: pforth
Section: interpreters
Priority: optional
Maintainer: Bdale Garbee <bdale@gag.com>
Build-Depends: debhelper (>= 13)
Standards-Version: 4.5.1
Homepage:  https://github.com/philburk/pforth
Vcs-Browser: https://salsa.debian.org/debian/pforth
Vcs-Git: https://salsa.debian.org/debian/pforth.git

Package: pforth
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Portable ANS-like Forth written in ANSI 'C'
 PForth is a public domain, portable Forth interpreter.
 .
 PForth is written in 'C' and can be easily ported to new 32 and 64-bit 
 platforms. It only needs character input and output functions to operate 
 and, therefore, does not require an operating system. This makes it handy 
 for bringing up and testing embedded systems.
 .
 PForth also works on desktops including Windows, Mac and Linux and supports 
 command line history. This lets you develop hardware tests on a desktop 
 before trying them on your embedded system. But pForth is not a rich and 
 friendly desktop programming environment. There are no GUI tools for 
 developing desktop applications. PForth is lean and mean and optimized for 
 portability.
 .
 PForth has a tool for compiling code on a desktop, then exporting the 
 dictionary in big or little endian format as 'C' source code. This lets you 
 compile tests for an embedded system that does not have file I/O.
 .
 PForth is based on ANSI-Forth but is not 100% compatible. 
 .
 Dcoumentation for PForth is available at http://www.softsynth.com/pforth/