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
|
Source: c-repl
Section: interpreters
Priority: extra
Maintainer: Robert S. Edmonds <edmonds@debian.org>
Build-Depends: debhelper (>= 5), dpatch
Standards-Version: 3.7.3
Package: c-repl
Architecture: any
Depends: ${shlibs:Depends}, ruby, libreadline-ruby
Description: read-eval-print loop for C
Many programming languages come with a REPL (read-eval-print loop), which
allows you to type in code line by line and see what it does. This is quite
useful for prototyping, experimentation, and debugging code.
.
Other programming languages, and especially C, use a "compile-run" model,
and don't provide a REPL. Let's fix that.
.
This approach is actually more of a read-eval loop, as c-repl doesn't know
anything about the types and parse trees of the code it's running. But
unlike other approaches to solving the "C interpreter" problem, c-repl
works directly with unmodified libraries and system headers.
.
This means you can experiment with a new library without writing a test
program or any bindings. Or just use it as a simple calculator, content in
knowing it is much faster than your neighbors using irb, like driving a
Ferarri on city streets.
|
