caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: proff@iq.org (Julian Assange)
To: Berke Durak <berke@altern.org>
Cc: Jeff Henrikson <jehenrik@yahoo.com>,
	caml-list@inria.fr, Mark Seaborn <mrs35@cam.ac.uk>
Subject: Re: [Caml-list] GCCXML: don't write your own C parser. (WAS: Rewriting UNIX . . .)
Date: Tue, 13 Nov 2001 16:10:18 +1100 (EST)	[thread overview]
Message-ID: <20011113051018.D646D259C1@suburbia.net> (raw)
In-Reply-To: <20011113015314.A13191@gogol.zorgol>

> A well-designed C syntax module, both parsing and unparsing, would be really
> great. It would be very useful for :
> 
> 1) Emitting C code (could be applied to FFTW or CamlIDL)

Or, bigloo like, parsing C .h files for transparent foreign function support.

--
 Julian Assange        |If you want to build a ship, don't drum up people
                       |together to collect wood or assign them tasks and
 proff@iq.org          |work, but rather teach them to long for the endless
 proff@gnu.ai.mit.edu  |immensity of the sea. -- Antoine de Saint Exupery
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


      reply	other threads:[~2001-11-13  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  5:17 [Caml-list] Rewriting UNIX in Caml and getting rid of the C disease Berke Durak
2001-11-11  6:11 ` Eric Newhuis
2001-11-11  8:22   ` Tom
2001-11-11 12:47 ` Sven
2001-11-11 13:32 ` Julian Assange
2001-11-12  8:32 ` Jeff Henrikson
2001-11-12 13:39 ` Mark Seaborn
2001-11-12 17:33   ` [Caml-list] GCCXML: don't write your own C parser. (WAS: Rewriting UNIX . . .) Jeff Henrikson
2001-11-13  0:53     ` Berke Durak
2001-11-13  5:10       ` Julian Assange [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011113051018.D646D259C1@suburbia.net \
    --to=proff@iq.org \
    --cc=berke@altern.org \
    --cc=caml-list@inria.fr \
    --cc=jehenrik@yahoo.com \
    --cc=mrs35@cam.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).