Update of /project/cparse/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv5664
Modified Files: index.html Log Message: added News and Plans sections, massaged other contents a bit
Date: Tue Mar 30 13:14:08 2004 Author: clynbech
Index: public_html/index.html diff -u public_html/index.html:1.1.1.1 public_html/index.html:1.2 --- public_html/index.html:1.1.1.1 Sun Mar 28 11:10:34 2004 +++ public_html/index.html Tue Mar 30 13:14:07 2004 @@ -17,16 +17,46 @@ <h3>Introduction</h3>
<p> - Cparse is a tool written by Timothy Moore to parse C header files + CPARSE is a tool written by Timothy Moore to parse C header files into FFI definitions. The tool will initially support only CMUCL FFI definitions but will be extended to support the generic UFFI library. </p>
<p> - Note that cparse is somewhat limited in its ability to understand - C header files. Other approaches certainly exists, for instance - <a href="http://www.ccs.neu.edu/home/lth/ffigen">FFIGEN</a>. + Current maintainer is Christian Lynbech. </p> + + <p> + Note that cparse is somewhat limited in its ability to understand C + header files. In particular, CPARSE does not have a concept of macros + as the header files are preprocessed prior to CPARSE handling. Other + approaches certainly exists, for instance <a + href="http://www.ccs.neu.edu/home/lth/ffigen%22%3EFFIGEN</a>. + </p> + + <h3>News</h3> + <table> + <tr> + <td valign="top" width="15%">2004/03/30</td> + <td valign="top" width="85%">This marks the release of version 0.2.4 + of cparse, the first release from its new home at + common-lisp.net. This release is a clean release of the sources + contributed by Timothy Moore. Its CVS tag is CPARSE_0_2_4.</td> + </tr> + </table> + + <h3>Plans</h3> + This are the current plans/ideas for CPARSE. Feel free to make further + suggestions on the mailing list. + <ul> + <li> Merge in Christians stuff. This includes a port to ACL FFI and the + start of a port to UFFI FFI. + <li> Investigate handling of "long long". + <li> Let CPARSE loose on random C header files and make a set of + examples. Try to clean out Linux/GCC'isms. + <li> Write automated tests for CPARSE. Franz' test harness seems + rather good so it will probably be based on that. + </ul>
<h3>Mailing Lists</h3> <ul>