/[cparse]/public_html/index.html
ViewVC logotype

Contents of /public_html/index.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.2 - (show annotations)
Tue Mar 30 18:14:07 2004 UTC (10 years ago) by clynbech
Branch: MAIN
CVS Tags: CPARSE_0_2_4, HEAD
Changes since 1.1: +34 -4 lines
File MIME type: text/html
added News and Plans sections, massaged other contents a bit
1 <?xml version="1.0"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
5 <head>
6 <title>CPARSE</title>
7 <link rel="stylesheet" type="text/css" href="style.css"/>
8 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
9 </head>
10
11 <body>
12 <div class="header">
13 <h1>CPARSE</h1>
14 <h2>Parsing C header files into FFI definitions</h2>
15 </div>
16
17 <h3>Introduction</h3>
18
19 <p>
20 CPARSE is a tool written by Timothy Moore to parse C header files
21 into FFI definitions. The tool will initially support only CMUCL FFI
22 definitions but will be extended to support the generic UFFI library.
23 </p>
24
25 <p>
26 Current maintainer is Christian Lynbech.
27 </p>
28
29 <p>
30 Note that cparse is somewhat limited in its ability to understand C
31 header files. In particular, CPARSE does not have a concept of macros
32 as the header files are preprocessed prior to CPARSE handling. Other
33 approaches certainly exists, for instance <a
34 href="http://www.ccs.neu.edu/home/lth/ffigen">FFIGEN</a>.
35 </p>
36
37 <h3>News</h3>
38 <table>
39 <tr>
40 <td valign="top" width="15%">2004/03/30</td>
41 <td valign="top" width="85%">This marks the release of version 0.2.4
42 of cparse, the first release from its new home at
43 common-lisp.net. This release is a clean release of the sources
44 contributed by Timothy Moore. Its CVS tag is CPARSE_0_2_4.</td>
45 </tr>
46 </table>
47
48 <h3>Plans</h3>
49 This are the current plans/ideas for CPARSE. Feel free to make further
50 suggestions on the mailing list.
51 <ul>
52 <li> Merge in Christians stuff. This includes a port to ACL FFI and the
53 start of a port to UFFI FFI.
54 <li> Investigate handling of "long long".
55 <li> Let CPARSE loose on random C header files and make a set of
56 examples. Try to clean out Linux/GCC'isms.
57 <li> Write automated tests for CPARSE. Franz' test harness seems
58 rather good so it will probably be based on that.
59 </ul>
60
61 <h3>Mailing Lists</h3>
62 <ul>
63 <li>
64 <a
65 href="http://www.common-lisp.net/mailman/listinfo/cparse">
66 CPARSE</a><br/>for discussion, questions, etc.</li>
67 <li>
68 <a
69 href="http://www.common-lisp.net/mailman/listinfo/cparse-devel">
70 CPARSE-devel</a><br/>for developers</li>
71 <li>
72 <a
73 href="http://www.common-lisp.net/mailman/listinfo/cparse-devel">
74 CPARSE-cvs</a><br/>CVS log feed.</li>
75 <li>
76 <a
77 href="http://www.common-lisp.net/mailman/listinfo/cparse-devel">
78 CPARSE-announce</a><br/>for announcements.</li>
79
80 </ul>
81
82 <h3>Download</h3>
83
84 <p>This project has not released any files.</p>
85
86 <h3>CVS</h3>
87
88 <p>You can <a
89 href="http://common-lisp.net/cgi-bin/viewcvs.cgi/cparse/?cvsroot=cparse">
90 browse our CVS repository</a> or download the current development tree via
91 anonymous cvs, as described
92 <a href="http://www.common-lisp.net/faq.shtml">here</a></p>
93
94 <div class="footer">
95 <a href="clynbech (at) common-lisp (dot) net">Christian Lynbech</a>,
96 18. Mar. 2004.
97 </div>
98
99 <div class="check">
100 <a href="http://validator.w3.org/check/referer">
101 Valid XHTML 1.0 Strict</a>
102 </div
103 </body>
104 </html>

  ViewVC Help
Powered by ViewVC 1.1.5