<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2009/10/a8a87b489f193e9e90dfe40cdf337a24"
  from="Elnatan Reisner &lt;elnatan@c...&gt;"
  author="Elnatan Reisner"
  date="2009-10-21T15:09:27"
  subject="Re: [Caml-list] Looking for C preprocessing language parser with OCAML interface"
  prev="2009/10/8be4cefc4f8ad9e31826f29359a52471"
  next="2009/10/3dc81b3ae87197fdc5af68dd25ec251d"
  prev-in-thread="2009/10/0618df357704f7f813388f5e6403ae7a"
  prev-thread="2009/10/46049b80e33839613edc2fc27b891a06"
  next-thread="2009/10/342c159172008d0992375924d6b0a684"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="Looking for C preprocessing language parser with OCAML interface">
<msg 
  url="2009/10/0618df357704f7f813388f5e6403ae7a"
  from="Yoonseok Ko &lt;ysko@r...&gt;"
  author="Yoonseok Ko"
  date="2009-10-21T12:29:16"
  subject="Looking for C preprocessing language parser with OCAML interface">
<msg 
  url="2009/10/a8a87b489f193e9e90dfe40cdf337a24"
  from="Elnatan Reisner &lt;elnatan@c...&gt;"
  author="Elnatan Reisner"
  date="2009-10-21T15:09:27"
  subject="Re: [Caml-list] Looking for C preprocessing language parser with OCAML interface">
</msg>
</msg>
</thread>

<contents>
On Oct 21, 2009, at 8:29 AM, Yoonseok Ko wrote:

&gt; I'm looking for a C preprocessing language parser with OCAML  
&gt; interface.

I was recently looking for such a tool myself, and I came across the  
link below mentioning Yacfe, from about a year ago. Unfortunately, it  
seems that the link provided there isn't working.
http://www.mail-archive.com/caml-list@yquem.inria.fr/msg01850.html

However, the project from which Yacfe was extracted, http://coccinelle.lip6.fr/ 
, is accessible. There might be something useful there.

-Elnatan

</contents>

</message>

